Browser content redirection
Browser content redirection prevents the rendering of webpages in the allow list on the VDA side. This feature uses Citrix Workspace app to instantiate a corresponding rendering engine on the client side, which fetches the HTTP and HTTPS content from the URL.
Browser content redirection supports the Google Chrome browser. Browser content redirection redirects the contents of a web browser to a client device, and creates a corresponding browser embedded within the Citrix Workspace app. This feature offloads network usage, page processing, and graphics appearing at the endpoint. Doing so improves the user experience when browsing demanding webpages, especially webpages that incorporate HTML5 or WebRTC video.
- Cookies are persistent across the sessions: When you exit and relaunch a browser, you aren’t prompted to reenter your credentials.
- Browsers now honor the language set on the local system.
For more information, see Browser content redirection.
Important:
- Browser content redirection can be enabled for 2402 LTSR using command-line
- It is enabled by default for all Current Releases of Citrix Workspace app for Windows.
- Browser content redirection is not supported for Citrix Workspace app LTSR 1912 and 2203.1 versions.
To enable Browser Content Redirection on VDA, make sure the following policies on Citrix Web Studio are enabled:
- Browser Content Redirection
- Browser Content Redirection ACL Configuration
- Browser Content Redirection Authentication Sites
Configure path for Browser Content Redirection overlay Browser temp data storage
You can configure the temp data storage path for the Chromium Embedded Framework (CEF) based browser. You can configure the path on VDA or client as follows:
On VDA:
-
Open the Registry Editor using
regediton the Run command. - Navigate to the
HKEY_LOCAL_MACHINE\Software\Citrix\DXMediaStream\ClientConfigurations\WindowsCefregistry path. -
Create the string entry BCRProfilePath and set its value to folder for CEF based BCRtmp files. For example:
"BCRProfilePath"="C:\\tmp\\AlternateBcrProfilePath" - Restart the session for the changes to take effect.
On client:
- Open the Registry Editor using
regediton the Run command. - Navigate to the
HKEY_CURRENT_USER\Software\Citrix\HdxMediaStreamregistry path. -
Create a registry value with the following attributes:
- Registry key name:
BCRProfilePath - Registry value: string
<folder for CEF based BCRtmp files>
- Registry key name:
- Restart the Citrix Workspace app for the changes to take effect.
Note:
Starting from Citrix Workspace app 2402 LTSR CU1 for Windows, the version of the Chromium Embedded Framework (CEF) is upgraded to 123. This version upgrade helps to resolve security vulnerabilities.
Limitations:
Browser Content Redirection has the following limitations:
- Doesn’t support Web Applications that require pop-up windows or session cookie persistence.
- Microsoft Internet Explorer isn’t supported.
- Applications that depend on the Google authentication service (For example, Google meet) are currently blocked.
- Extension plug-in isn’t officially published on Microsoft Edge currently. However, there’s a workaround to it.
- HTML5 video redirection policy must be disabled when Browser Content Redirection is in use.
- Sometimes, end users might be disconnected from their sessions because of unreliable networks, highly variable network latency, or range limitations of wireless devices. Browser Content Redirection doesn’t have sufficient fallback or reporting mechanism for such scenarios.
- Files downloaded through the overlay are locally stored (on the end user’s client machine).
Improved performance of BCR
Previously, BCR used client-side disk space cache and the cached information wasn’t deleted during an upgrade. This setting resulted in higher disk space usage over time and inconsistent behavior while a page is redirected using BCR.
To resolve this issue, BCR uses an in-memory cache. This enhancement helps to improve the performance of BCR.
This feature is disabled by default. You can enable this feature on VDA or client as follows:
On VDA:
-
Open the Registry Editor using
regediton the Run command. -
Navigate to the
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\HDXMediaStream\ClientConfigurations\WindowsCefregistry path. -
Create a
DWORDkey by the nameBCRStoreCEFCacheInMemoryand set the value of the key to 1.
If the value of BCRStoreCEFCacheInMemory is set to 0, BCR uses client disk space.
On client:
-
Open the Registry Editor using
regediton the Run command. -
Navigate to the
HKEY_CURRENT_USER\Software\Citrix\HDXMediaStreamregistry path. -
Create a
DWORDkey by the nameBCRStoreCEFCacheInMemoryand set the value of the key to 1.
If the value of BCRStoreCEFCacheInMemory is set to 0, BCR uses client disk space.
Note:
If the
BCRStoreCEFCacheInMemoryis set on both client and VDA, the setting on client takes precedence.If both
BCRProfilePathandBCRStoreCEFCacheInMemoryare set, the configuration forBCRProfilePathtakes precedence and the configuration forBCRStoreCEFCacheInMemoryis ignored.
Limitation:
The in-memory cache size limit is set to 10MB.