Orign header rewrite policy issues

Orign header rewrite policy issues

book

Article ID: CTX296987

calendar_today

Updated On:

Description

  • Header is not inserting
  • Issue with CORS in SharePoint wherein customer is trying to rewrite origin header so that application works.
  • Issue is only with chrome or Firefox browser its working as expected while accessing from IE browser.
  • Customer is using advanced CVPN as a reverse proxy.
  • Tried binding policy the origin headers does not get rewritten. configured the policies as:- add rewrite action rw_act_replacehdr_origin replace "http.RES.HEADER(\"Access-Control-Allow-Origin\")" "\"https://example.office.com\"" add rewrite policy rw_pol_replacehdr_origin true rw_act_replacehdr_origin
  • Customer has bookmarks configured user will click on mylgc and once it got open the complete page is not loading via chrome browser contents were not loading .
  • When we checked on F12 developer toll we are Page could not be loaded.

Resolution

Issue is specific to Chrome and Firefox, In IE it's working.   This is by design.  https://docs.citrix.com/en-us/citrix-gateway/current-release/vpn-user-config/clientless-vpn-access/advanced-clientless-vpn-access.html
 

Caveats

The advanced clientless VPN is aimed at providing access to Enterprise Web apps. Such apps have only one FQDN for every kind of resource they need (JavaScript, css, images, and so on). Since we encode the complete FQDN of internal apps into a single-octet (clientless VPN), we lose out on the subdomain relationship. As a result, whenever an Enterprise WebApp is configured with CORS, sometimes you might notice issues while accessing it over the advanced clientless VPN.


Problem Cause

Its the limitation on CVPN.

Additional Information

https://docs.citrix.com/en-us/citrix-gateway/current-release/vpn-user-config/clientless-vpn-access/advanced-clientless-vpn-access.html

Caveats

The advanced clientless VPN is aimed at providing access to Enterprise Web apps. Such apps have only one FQDN for every kind of resource they need (JavaScript, css, images, and so on). Since we encode the complete FQDN of internal apps into a single-octet (clientless VPN), we lose out on the subdomain relationship. As a result, whenever an Enterprise WebApp is configured with CORS, sometimes you might notice issues while accessing it over the advanced clientless VPN.