Jump to: navigation, search

Genesys Co-browse Server Release Notes

Release Date Release Type Restrictions AIX Linux Solaris Windows
03/11/16 Hot Fix X

Helpful Links

Releases Info

Product Documentation

Genesys Co-browse

Genesys Products

List of Release Notes

What's New

This release contains the following new features and enhancements:

  • Co-browse now logs an error when the Co-browse proxy cannot load an image, a font, or CSS. Each failure to load a resource through the url-proxy or css-proxy creates an exception stack trace in the Co-browse log with a severity of warning.
  • Customers can now turn off document.domain modification using the setDocumentDomain option in the instrumentation script.

    Option name: setDocumentDomain
    Valid values: true, false
    Default value: true

    Determines if Co-browse sets the document.domain property. If set to true, Co-browse modifies the document.domain property. If set to false, Co-browse does not modify document.domain.

    Co-browse modifies document.domain to support cross-subdomain communication between iframes and the topmost context.

Resolved Issues

This release contains the following resolved issues:

Fixed an issue where improperly unset session cookies gave a Session ID is invalid or has expired error when a consumer left and re-joined a co-browse session. Previously, this error could occur when co-browsing on a third or lower level domain such as http://sub.domain.com while using cookie-based stickiness and long-polling transport. (CB-3476)

Improved synchronization stability of dynamic content in interactive pages. Previously, web page elements created using JavaScript did not always correctly synchronize click events. (CB-3475)

Fixed an issue where Internet Explorer would some times throw an exception when using the cssText property. (CB-3472)

The Co-browse url-proxy now correctly unpacks gzip-encoded resources. Previously, the url-proxy returned errors such as ERR_CONTENT_DECODING_FAILED when fetching gzip encoded resources. (CB-3463)

Upgrade Notes

No special procedure is required to upgrade to release

This page was last modified on March 11, 2016, at 11:17.


Comment on this article:

blog comments powered by Disqus