Static Resource Synchronization

Starting in release 9.0.00x.xx, Genesys Co-browse can cover web sites that are fully authenticated, without any need for deploying and configuring intermediate proxy equipment.

Genesys Co-browse can synchronize resources that are placed behind authentication.

This feature also allows us to sync resources without proxying them through Co-browse server and this makes Co-browse tuning easier (no need to set allowedExternalDomains option, which is a big problem especially for Cloud).

Slave side is supposed to load more quickly since resources are stored on Co-browser server and are not taken from their original host and proxied every time. (This however will not be true for first session establishment, when resources are not cached yet, but will be true for all further sessions)

The 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.

section [Redis], option: cache.ttl

Retention policy for 2-level cache: used to determine how much time resources will be stored in 2-level cache, if left untouched.

Possible values: any duration, like 1d/1h/30min/30m/3600s/3600sec Default value: 1d

Retention policy for 1-level cache (local cache) is 30 minutes, not changeable.

dev note: TTL prolongation (when file is touched) is not made for CSS files and its nested resources (see CB-5758 - Nested cached file will not be cached again after being changed if outer file wasn't changed CLOSED for details). dev note 2: in some very special cases resources can be cleared by removing CacheEntity* keys from Redis.

This feature needs customer documentation. Proposed sections:

new capabilities of Co-browse: synchronizing resources placed behind authentication

configuration options, default and recommended settings and limits (see Configuration and feature control)

known limitations (see Limits and Constraints, pay attention to CORS configuration)

note about allowedExternalDomains:

resource is cached even if its location is not included in allowedExternalDomains configuration option

when resource is not cached successfully, there is an attempt to load it directly from its original location on agent side and this is done even if location is not included in allowedExternalDomains

Resource synchronization mechanism compatibility

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, it must have properly set CORS headers, as co-browse script on master side side needs to access its content.