Jump to: navigation, search

session Section


Default Value: None
Valid Values:

  • HTTP-based URLs, such as http://localhost/cobrowse/my-dom-restrictions.xml
  • File-based based URLs, such as file:C:/my-dom-restrictions.xml

Changes Take Effect: For new Co-browse sessions

Specifies the URL to the DOM restrictions XML file. If nothing is specified, the default DOM restrictions policy is applied, which prevents agents from clicking submit buttons. For more information, see DOM Restrictions in the Developer's Guide.

Data masking is enabled in the system for all password inputs and cannot be changed by the DOM restrictions XML file.
HTTP hosting of a DOM restrictions XML resource requires additional considerations:
  1. The XML web resource should return a Last-Modified header.
  2. If the XML web resource is hosted on a web server that is only accessible through a proxy, the proxy settings (http://docs.oracle.com/javase/7/docs/api/java/net/doc-files/net-properties.html) must be set using JVM system properties in setenv.bat/sh. For example:
    set JAVA_OPTS=%JAVA_OPTS% -Dhttp.proxyHost=<host> -Dhttp.proxyPort=<port>


Default Value: 600
Valid Values: Any positive integer
Changes Take Effect: For new Co-browse sessions

Specifies, in seconds, the period of inactivity during a Co-browse session before the agent joins. Once the agent joins, the session becomes active. If a session does not become active within this period, it is automatically deactivated.


Default Value: true
Valid Values:true or false
Changes Take Effect: For new Co-browse sessions

Specifies if agents are allowed to send customers a request to enter Write Mode. If false, the UI button to request Write Mode will not be available to agents.

This page was last edited on June 15, 2015, at 22:01.
Comments or questions about this documentation? Contact us for support!