Static Resource Synchronization

Starting in release 9.0.005.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).

Why does Co-browse need to sync static resources?

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.

Synchronizing the resources

Co-browse is able to reach all resources, cache them, and then provide them directly to the agent-side (also referred to as the slave-side). The synced resources can be images, CSS stylesheets, fonts, and resources from style tags.

If caching fails for a resource, Co-browse will try other ways to sync the resource to the agent side. By default configuration, for the resource where caching failed, Co-browse will attempt to sync the resource to the agent-side via server-side sync and/or to get it directly from its location.

The back-up mechanism depends on the type of the resource, its location, and Co-browse configuration. link to server side sync https://docs.genesys.com/Documentation/GCB/latest/Deployment/CSSsynchronization

server-side css sync mechanism can be disabled in js configuration, option 'css'. https://docs.genesys.com/Documentation/GCB/latest/API/JSConfigAPI

<script> var _genesys = {

   cobrowse: {
       css: {
         server: false
       }
   }

}; </script> in this case if caching failed for some resource, there will be only an attempt to load it directly from its location.

Permalink

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

For information about known issues, see the Co-browser Server 9.0.x Release Note.