document.domain deprecation on Chrome 115
Article ID: CTX580661
Updated On:
Description
Issue with HTTP response if the page is reliant on document.domain.
Same-origin policy by setting document.domain is deprecated, and will be disabled by default.
Environment
Citrix is not responsible for and does not endorse or accept any responsibility for the contents or your use of these third party Web sites. Citrix is providing these links to you only as a convenience, and the inclusion of any link does not imply endorsement by Citrix of the linked Web site. It is your responsibility to take precautions to ensure that whatever Web site you use is free of viruses or other harmful items.
Resolution
Refer to the following link for two possible workaround methods: https://developer.chrome.com/blog/document-domain-setter-deprecation/
Problem Cause
Chrome disables modifyingdocument.domain.
https://developer.chrome.com/blog/document-domain-setter-deprecation/#origin-agent-cluster
You will see the following error message:
Issue/Introduction
This article denotes how you may use a Citrix Netscaler that Load Balances backend web services broken by the deprecation of document.domain on Chrome's releases after 115, to workaround the break until the web app is updated.
Additional Information
- https://docs.netscaler.com/en-us/citrix-adc/current-release/appexpert/rewrite.html
- https://docs.netscaler.com/en-us/citrix-adc/current-release/ssl/how-to-articles/configure-ssl-based-header-insertion.html
- https://docs.netscaler.com/en-us/citrix-adc/current-release/optimization/integrated-caching/configure-cookies-headers-and-polling.html#inserting-http-headers-at-response-time
Was this article helpful?
Yes
No
Powered by
