Browser content redirection prevents the rendering of whitelisted webpages on the VDA side. This feature uses Citrix Receiver to instantiate a corresponding rendering engine on the client side, which fetches the HTTP and HTTPS content from the URL.
You can specify that webpages be redirected to the VDA side (and not redirected on the client side) by using a blacklist.
This overlay web layout engine runs on the endpoint device instead of on the VDA and uses the endpoint CPU, GPU, and RAM.
Only the browser viewport is redirected. The viewport is the rectangular area in your browser where content displays. The viewport doesn't include things like the Address Bar, Favorites Toolbar, Status Bar. Those items are in the user interface.
Here are scenarios of how Citrix Receiver fetches content:
There might be times when client redirection fails. For example, if the client machine does not have direct internet access, an error response might go back to the VDA. In such cases, the Internet Explorer browser on the VDA can then reload and render the page on the server.
You can suppress server rendering of video elements by using the existing Windows media fallback prevention policy. Set this policy to Play all content only on client or Play only client-accessible content on client. These settings block video elements from playing on the server if there are failures in client redirection. This policy takes effect only when browser content redirection is enabled and the URL that falls back is in the Access Control List policy. The URL can't be in the blacklist policy.
Client operating system:
Windows 7, 8.x, or 10 and Internet Explorer 11.
Citrix Receiver for Windows minimum version 4.10
Citrix Receiver for Linux minimum version 13.9
XenApp and XenDesktop 7.17, 7.16:
VDA operating system: Windows 10 (minimum version 1607), Windows Server 2012 R2, Windows Server 2016
Browser on the VDA: Internet Explorer 11 and configure these options:
Client side optimization for Citrix Receiver for Windows 4.10
HdxBrowser.exe is the overlay browser on the endpoint that is responsible for client-side rendering. To enable HdxBrowser.exe to use the GPU resources on the client, set these registry keys on the Windows endpoint.
Editing the registry 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.
\HKEY_LOCAL_MACHINE \SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_GPU_RENDERING (create if not present)
\HKEY_CURRENT_USER) \SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_GPU_RENDERING (create if not present)
Value name: HdxBrowser.exe
Value data: 00000001