Server Host to Client URL Content Redirection and Validation
Article ID: CTX261938
Updated On:
Description
When using Host to Client URL Redirection a specific URL may fail to open on the client as expected and instead open on the VDA. Other URL links will succeed in redirecting properly.
Environment
Caution! Using Registry Editor incorrectly can cause serious problems that might require you to reinstall your operating system. Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. Be sure to back up the registry before you edit it.
Resolution
Make sure that the URL link being redirected is accessible from the client and that the "base URL" of the link responds to the HTTP "HEAD" method with a 200 OK response.
Example of Base URL
If the link being redirected is: https://webserver1.contoso.com/auth/login.asp
The Base URL being checked by Receiver/Workspace app is https://webserver1.contoso.com
If the web server will not respond to a HEAD request to the base URL you can alternatively configure the Citrix Receiver / Workspace App on the endpoint to send a GET request instead by setting the following Registry Key:
From LC0326 - first included in Receiver for Windows 3.4 CU4 .
Occasionally, accessing a web site that contains a "HEAD" request in the URL header instead of a "GET" request might fail if the web server fails to accept the HEAD request. As a result, server-to-client content redirection does not work.
To enable the fix, create the following registry key:
HKEY_CURRENT_USER_\Software\Citrix\ICA Client\Engine
Name: SpecificSites
Type: REG_MULTI_SZ
Enter the base URL of the site(s), one per line, you which you want to have a GET request sent instead of HEAD.
If the webserver responds with a 200 OK to the GET request, content redirection should succeed.
If Citrix Receiver/Workspace App receives 200 OK response back it assumes it is safe to redirect the URL and have it open on the client. If it does *not* receive a 200 OK response back it rejects the URL redirection request and tells the VDA to open it there instead rather than risk the user not being able to access the URL at all.
Example of Base URL
If the link being redirected is: https://webserver1.contoso.com/auth/login.asp
The Base URL being checked by Receiver/Workspace app is https://webserver1.contoso.com
If the web server will not respond to a HEAD request to the base URL you can alternatively configure the Citrix Receiver / Workspace App on the endpoint to send a GET request instead by setting the following Registry Key:
From LC0326 - first included in Receiver for Windows 3.4 CU4 .
Occasionally, accessing a web site that contains a "HEAD" request in the URL header instead of a "GET" request might fail if the web server fails to accept the HEAD request. As a result, server-to-client content redirection does not work.
To enable the fix, create the following registry key:
HKEY_CURRENT_USER_\Software\Citrix\ICA Client\Engine
Name: SpecificSites
Type: REG_MULTI_SZ
Enter the base URL of the site(s), one per line, you which you want to have a GET request sent instead of HEAD.
If the webserver responds with a 200 OK to the GET request, content redirection should succeed.
Problem Cause
The Host to Client Content Redirection feature includes a sanity check to ensure that the endpoint can actually reach the URL being redirected. Citrix Receiver/Workspace App implements this check by sending (from the client) a HEAD method request to the base FQDN of the URL being redirected.If Citrix Receiver/Workspace App receives 200 OK response back it assumes it is safe to redirect the URL and have it open on the client. If it does *not* receive a 200 OK response back it rejects the URL redirection request and tells the VDA to open it there instead rather than risk the user not being able to access the URL at all.
Issue/Introduction
Drop Files
The Host to Client Content Redirection feature includes a sanity check to ensure that the endpoint can actually reach the URL being redirected. Citrix Receiver/Workspace App implements this check by sending (from the client) a HEAD method request to the base FQDN of the URL being redirected.
Additional Information
Was this article helpful?
Yes
No
Powered by
