-
-
Bidirectional content redirection
-
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
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:
- Internet Explorer 11
- 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
Bidirectional content redirection must be enabled using the Citrix policy on both the VDA and client for redirection to work. Bidirectional content redirection is disabled by default.
For VDA configuration, see Bidirectional content redirection in the ICA policy settings.
For client configuration, see Bidirectional content redirection in the Citrix Workspace app for Windows documentation.
Browser extensions must be registered using the commands shown. Run the commands as needed on the VDA and client based on the browser in use.
To register the browser extensions on the VDA, open a command prompt. Then, run %ProgramFiles(x86)%\Citrix\HDX\bin\vdaredirector.exe with the required browser option as shown in the examples shown:
%ProgramFiles(x86)%\Citrix\HDX\bin\vdaredirector.exe /regIE
%ProgramFiles(x86)%\Citrix\HDX\bin\vdaredirector.exe /regChrome
%ProgramFiles(x86)%\Citrix\HDX\bin\vdaredirector.exe /regEdge
To register the extension on all available browsers run:
%ProgramFiles(x86)%\Citrix\HDX\bin\vdaredirector.exe /regall
To unregister a browser extension use the /unreg<browser> option as in the example shown:
%ProgramFiles(x86)%\Citrix\HDX\bin\vdaredirector.exe /unregIE
To register the browser extensions on the client open a command prompt and run %ProgramFiles(x86)%\Citrix\ICA Client\redirector.exe with the same options as the examples shown.
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.
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.
In Citrix Studio, set the wildcard URL in Allowed URLs to be redirected to Client. The asterisk (*) is the wildcard character.
NOTE:
- Don’t set the Allowed URLs to be redirected to VDA in the client policy. Ensure that the sites set the Allowed URLs to be redirected to VDA to avoid infinite redirection loops.
- Top-level domains are not supported. For example,
https://www.citrix.*orhttp://www.citrix.co*is not redirected.
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. - Only HTTP/HTTPS protocol URLs are supported. 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.
Share
Share
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.