Static Resource Synchronization

Starting in release 9.0.004.xx, Genesys Co-browse can be used with websites that are fully authenticated, without the need for deploying and configuring intermediate proxy equipment, or without the need for domain whitelisting (that is, no need to configure the allowedExternalDomains option).

Synchronizing resources that are placed behind authentication, provides Co-browse with an opportunity to render a web page the same way for both the customer and the agent, enabling them to have a fully synced co-browsing experience. Static resources that are not synced can result in different page views or 401 unauthorized error messages during a co-browsing session.

The synced resources can be images, CSS stylesheets, fonts, and resources from style tags.

Configuring static resource synchronization

• The enableStaticResourceService option of the JavaScript Configuration API manages the static resource synchronization. This option is set to false by default. Setting this option to true turns on the feature, and resources will be cached.

• The [redis] cache.ttl configuration option specifies the retention policy for 2-level cache and is used to determine how much time the resource will be stored. This option is set to 1d by default. Note that the retention policy for 1-level cache (local cache) is 30 minutes, and is not configurable.

Important

• The resource is cached even if its location is not included in the allowedExternalDomains configuration option.
• If the resource is not successfully cached, there is an attempt to load it directly from its original location on the agent side. This occurs even if the location is not included in the allowedExternalDomains configuration option.

Limitations

• pseudoHover for cached files is not supported. Hover effects can work improperly for elements whose styles are described in cached CSS files or style tags.

• If a resource for caching is received from a third-party domain, the CORS headers must be correctly set, since the Genesys Co-browse script on the master-side needs to access its content.

• Resources added or updated after a co-browse session has started are not cached and are taken by the slave-side via direct link to the resource or proxied through the Co-browse Server.

• Images from <source> tags of the <picture> tag are not cached.

• Resources from style attributes of DOM nodes are not cached and are taken by the slave-side via direct link to the resources.