Content redirection allows you to control whether users access information with applications published on servers or with applications running locally on user devices.
Host to client redirection is one kind of content redirection. It is supported only on Server OS VDAs (not Desktop OS VDAs).
Host to client redirection was previously known as server to client redirection.
You might consider using host to client redirection in specific but uncommon cases, for performance, compatibility, or compliance. Normally, other forms of content redirection are better.
Performance
You can use host to client redirection for performance, so that whenever an application is installed on the user device, it is used in preference to an application on the VDA.
Keep in mind that host to client redirection will improve performance only under specific conditions, because the VDA already optimizes Adobe Flash and other types of multimedia content. First, consider using the other approaches (policy settings) noted in the tables below, rather than host to client redirection; they offer more flexibility and usually give a better user experience, particularly for less-powerful user devices.
Compatibility
You can use host to client redirection for compatibility in the following use cases:
Compliance
You can use host to client redirection for compliance in the following use cases:
Some situations are more likely in complex environments, and also if the user device and the VDA belong to different organizations.
Environments may have many different types of user devices.
User device |
Situation or environment |
Content redirection approach |
Tablet |
- |
Any approach (see next table) |
Laptop PC |
- |
Any approach (see next table) |
Desktop PC |
Users use a wide range of apps installed on the user device |
Any approach (see next table) |
Desktop PC |
Users use only a few known apps that are installed on the user device |
Local App Access |
Desktop PC |
Users use no apps installed on the user device |
Multimedia redirection and/or Flash redirection |
Desktop appliance |
Vendor supports multimedia redirection and/or Flash redirection |
Multimedia redirection and/or Flash redirection |
Thin client |
Vendor supports multimedia redirection, Flash redirection, and host to client redirection |
Any approach (see next table) |
Zero client |
Vendor supports multimedia redirection and/or Flash redirection |
Multimedia redirection and/or Flash redirection |
Use the following examples to help guide your content redirection approach.
URLs link |
Situation or environment |
Content redirection approach |
A web page or document |
The VDA cannot access the URL |
Host to client redirection |
A web page |
The web page contains Adobe Flash |
Flash redirection |
A multimedia file or stream |
The VDA has a compatible multimedia player |
Multimedia redirection |
A multimedia file or stream |
The VDA does not have a compatible multimedia player |
Host to client redirection |
A document |
The VDA does not have an application for that document type |
Host to client redirection |
A document |
The document must not be downloaded to the user device |
No redirection |
A document |
The document must not be uploaded to the VDA |
Host to client redirection |
A custom URL type |
The VDA does not have an application for that custom URL type |
Host to client redirection |
Host to client redirection is supported by Citrix Receiver for Windows, Receiver for Mac, Receiver for Linux, Receiver for HTML5, and Receiver for Chrome.
To use host to client redirection, the user device must have a web browser, multimedia player, or other application that is suitable for the content. If the user device is a desktop appliance, thin client, or zero client, confirm that it has suitable applications and is sufficiently powerful.
User devices enabled for Local App Access use a different mechanism for content redirection, and do not require host to client content redirection.
You can use Citrix policies to prevent host to client content redirection for unsuitable devices.
Host to client redirection is used when URLs are:
Host to client redirection is not used for URLs in a web browser (either in a web page or entered in the address bar of the web browser).
If users change their default web browser on the VDA (for example, by using Set Default Programs), that change can interfere with host to client redirection for applications.
When host to client content redirection is enabled, the app that is used to open the URL depends on the configuration of the user device for both the URL type and the content type. For example:
This user device configuration is not controlled by host to client content redirection. If you do not control the configuration of the user device, consider using Flash redirection and multimedia redirection, rather than host to client content redirection.
The following URL types are opened locally through user devices when host to client redirection is enabled:
You can change the list of URL types for host to client redirection, to remove and add URL types, including custom URL types.
Enabling host to client redirection starts with enabling a Citrix policy setting.
The Host to client redirection policy setting is located in the File Redirection policy settings section. By default, this setting is disabled.
In addition, you may need to set registry keys and Group Policy for the server VDAs, depending on the VDA's OS.
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.
- Reg file start --
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\ServerFTAHTML\shell\open\command]
@="\"C:\\Program Files (x86)\\Citrix\\system32\\iexplore.exe\" %1"
[HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\ServerFTA]
@="ServerFTA"
[HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\ServerFTA\Capabilities]
"ApplicationDescription"="Server FTA URL."
"ApplicationIcon"="C:\\Program Files (x86)\\Citrix\\system32\\iexplore.exe,0"
"ApplicationName"="ServerFTA"
[HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\ServerFTA\Capabilities\URLAssociations]
"http"="ServerFTAHTML"
"https"="ServerFTAHTML"
[HKEY_LOCAL_MACHINE\SOFTWARE\RegisteredApplications]
"Citrix.ServerFTA"="SOFTWARE\\Citrix\\ServerFTA\\Capabilities"
-- Reg file end --
Create an XML file. Copy the text between "xml file start" and "xml file end" below, paste it in the XML file, and then save the file as ServerFTAdefaultPolicy.xml.
-- xml file start --
<?xml version="1.0" encoding="UTF-8"?>
<DefaultAssociations>
<Association Identifier="http" ProgId="ServerFTAHTML" ApplicationName="ServerFTA" />
<Association Identifier="https" ProgId="ServerFTAHTML" ApplicationName="ServerFTA" />
</DefaultAssociations>
-- xml file end --
From the current Group Policy Management Console, navigate to: Computer configuration > Administrative Templates > Windows Components > File Explorer > Set a default associations configuration file, and provide the ServerFTAdefaultPolicy.xml file you created.
To change the list of URL types for host to client redirection, set the following registry key on the server VDA.
Key: HKLM\Software\Wow6432Node\Citrix\SFTA
To remove URL types from the list, set DisableServerFTA and NoRedirectClasses:
Name: DisableServerFTA
Type: REG_DWORD
Data: 1
Name: NoRedirectClasses
Type: REG_MULTI_SZ
Data: Specify any combination of the values: http, https, rtsp, rtspu, pnm, or mms. Enter multiple values on separate lines. For example:
http
https
rtsp
To add URL types to the list, set ExtraURLProtocols:
Name: ExtraURLProtocols
Type: REG_MULTI_SZ
Data: Specify any combination of URL types. Each URL type must include the :// suffix; separate multiple values with semicolons. For example:
customtype1://;customtype2://
To enable host to client redirection for a specific set of web sites, set the following registry key on the server VDA.
Key: HKLM\Software\Wow6432Node\Citrix\SFTA
Name: ValidSites
Type: REG_MULTI_SZ
Data: Specify any combination of fully-qualified domain names (FQDNs). Enter multiple FQDNs on separate lines. An FQDN may include a wildcard in the leftmost position only. This matches a single level of domain, which is consistent with the rules in RFC 6125. For example:
www.example.com
*.example.com