Citrix Virtual Apps and Desktops

Bidirectional content redirection

Bidirectional content redirection allows HTTP or HTTPS URLs in web browsers, or embedded into applications, to be forwarded between the Citrix VDA session and the client endpoint in both directions. A URL entered in a browser running in the Citrix session can be opened using the client’s default browser. Conversely, a URL entered in a browser running on the client can be opened in a Citrix session, either with a published application or desktop. Some common use cases for bidirectional content redirection include:

  • Redirection of web URLs in cases where the starting browser does not have network access to the source.
  • Redirection of web URLs for browser compatibility and security reasons.
  • Redirection of web URLs embedded in applications when running a web browser on the Citrix session or the client isn’t wanted.

System requirements

  • Single-session or multi-session OS VDAs
  • Citrix Workspace app for Windows

Browsers:

  • Google Chrome with Citrix Browser Redirection Extension (available on the Google Chrome Web Store)
  • Microsoft Edge (Chromium) with Citrix Browser Redirection Extension (available on the Google Chrome Web Store)

Configuration

Starting in Citrix Virtual Apps and Desktops version 2311, bidirectional content redirection is configured through Citrix Studio only. Prior releases had policy settings configured on both the client endpoint and Studio. Bidirectional content redirection is disabled by default.

For VDA configuration, see Bidirectional content redirection in the ICA policy settings.

For browser redirection to work, browser extensions must be registered on the originating browser (where the URL is redirected from) using the commands shown. Run the commands as needed on the VDA and client, based on the browser in use.

Browser VDA Client
Google Chrome %ProgramFiles(x86)%\Citrix\HDX\bin\vdaredirector.exe /regChrome %ProgramFiles(x86)%\Citrix\ICA Client\redirector.exe /regChrome
Microsoft Edge %ProgramFiles(x86)%\Citrix\HDX\bin\vdaredirector.exe /regEdge %ProgramFiles(x86)%\Citrix\ICA Client\redirector.exe /regEdge
All Available Browsers %ProgramFiles(x86)%\Citrix\HDX\bin\vdaredirector.exe /regall %ProgramFiles(x86)%\Citrix\ICA Client\redirector.exe /regall

To unregister a browser extension:

Browser VDA Client
Google Chrome %ProgramFiles(x86)%\Citrix\HDX\bin\vdaredirector.exe /unregChrome %ProgramFiles(x86)%\Citrix\ICA Client\redirector.exe /unregChrome
Microsoft Edge %ProgramFiles(x86)%\Citrix\HDX\bin\vdaredirector.exe /unregEdge %ProgramFiles(x86)%\Citrix\ICA Client\redirector.exe /unregEdge
All Available Browsers %ProgramFiles(x86)%\Citrix\HDX\bin\vdaredirector.exe /unregall %ProgramFiles(x86)%\Citrix\ICA Client\redirector.exe /unregall

Note:

The register command causes Chrome and Edge browsers to prompt users to enable the Citrix Browser Redirection Extension during first launch. The browser extension can also be installed manually from the Google Chrome Web Store. For Microsoft Edge, also see Add an extension to Microsoft Edge from the Chrome Web Store.

Wildcard redirection from Citrix VDA to client

Bidirectional content redirection supports the use of wildcards when defining the URLs to be redirected. To configure bidirectional content redirection, see the configuration instructions.

Custom protocol redirection from VDA to client

Bidirectional content redirection supports redirecting custom protocols from the Citrix VDA to the client. Protocols other than HTTP or HTTPS are supported. To configure bidirectional content redirection, see the configuration instructions.

In Web Studio, set the custom protocol in Bidirectional content redirection.

Note:

  • You must have administrator privileges to run these commands.

  • The client must have an application registered to handle the protocol. Otherwise, the URL redirects to the client and fails to launch.
  • Custom protocol URLs that you enter or launch in the Chrome and Edge browsers are not supported and not redirected.
  • The following protocols are not supported: rtsp://, rtspu://, pnm://, mms://.

Other considerations

  • Browser requirements and configurations are only applicable to the browser starting the redirection. The destination browser, where the URL opens after redirection is successful, isn’t considered for support. When redirecting URLs from the VDA to a client, a supported browser configuration is only required on the VDA. Conversely, when redirecting URLs from the client to a VDA, a supported browser configuration is only required on the client. Redirected URLs are handed off to the default browser configured on the destination machine, either the client or the VDA, depending on direction. Using the same browser type on the VDA and the client is not required.
  • Check that redirection rules do not result in a looping configuration. For example, a VDA policy is set to redirect https://www.citrix.com, and the client policy is set to redirect the same URL, resulting in infinite looping.
  • URL shorteners aren’t supported.
  • Client-to-VDA redirection requires the Windows client to be installed with administrator rights.
  • If the destination browser is already open, the redirected URL opens in a new tab. Otherwise, the URL opens in a new browser window.
  • Bidirectional content redirection does not work when Local App Access (LAA) is enabled.
Bidirectional content redirection