The URL Content Redirection feature has certain requirements and limitations.

URL Content Redirection Feature Requirements

The URL Content Redirection feature has the following requirements:

  • Horizon Client for Windows 4.0 or later.

  • Horizon Client for Mac 4.2 and 4.3. URL Content Redirection is a Tech Preview feature that supports only agent-to-client redirection.

  • The supported browsers in which you can type or click a URL and have that URL redirected are Internet Explorer 9,10, and 11.

  • The display protocol for the remote session must be VMware Blast or PCoIP.

URL Content Redirection Feature Limitations

The behavior of the URL Content Redirection feature might have the following unexpected results:

  • If the URL opens a country-specific page based on the locale, the locale page that is opened is determined by the source of the link. For example, if the remote desktop (agent source) resides in a data center in Japan and the user's computer resides in the U.S., if the URL is redirected from the agent to the client machine, the page that opens on the U.S. client is the Japanese page.

  • If users create favorites from Web pages, the favorites get created after redirection. For example, say a user clicks a link on the client machine and the URL is redirected to a remote desktop (agent). If the user creates a favorite for that page, the favorite gets created on the agent. The next time the user opens the browser on the client machine, the user might expect to find the favorite on the client machine, but the favorite was stored on the agent (remote desktop).

  • Files that users download are downloaded to the machine whose browser was used to open the URL, for example, if a user clicks a link on the client machine and the URL is redirected to a remote desktop. If the link was for downloading a file, or if the link is for a Web page where the user downloads a file, the file is downloaded to the remote desktop rather than the client machine.

Unsupported URL Content Redirection Features

The URL Content Redirection feature does not work in the following circumstances:

  • Shortened URLs such as https://goo.gl/abc can be redirected based on filtering rules, but the filtering mechanism does not look at the original un-shortened URL. For example, if you have a rule that redirects URLs containing acme.com, an original URL such as http://www.acme.com/some-really-long-path, and a shortened URL of the original URL such as https://goo.gl/xyz, the original URL is redirected but not the shortened URL.

    Workaround: Create rules to block or redirect URLs from the Web sites most often used for shortening URLs.

  • Embedded HTML pages will bypass URL redirection. For example, say a user goes to a URL that does not match a URL redirection rule. If page contains an embedded HTML page (an iFrame or inline frame) whose URL does match a redirection rule, the URL redirection rule does not work. The rule works only on the top-level URL.

  • URL Content Redirection does not work in situations where Internet Explorer plug-ins are disabled, for example, when the user switches to InPrivate Browsing in Internet Explorer. (People use private browsing so that Web pages and files downloaded from Web pages will not be logged in to the browsing and download history on their computer.) This limitation arises because the URL Redirection feature requires a certain Internet Explorer plug-in to be enabled, and private browsing disables these plug-ins.

    Workaround: Use the GPO setting to prevent users from disabling plug-ins. These settings include the following: "Do not allow users to enable or disable add-ons" and "Automatically enable newly installed add-ons." In the Group Policy Management Editor, these settings can be found under Computer Configuration > Administrative Templates > Windows Components > Internet Explorer.

    Workaround specifically for Internet Explorer: Use the GPO setting to disable InPrivate mode. This setting is called "Turn off InPrivate Browsing." In the Group Policy Management Editor, these settings can be found under Computer Configuration > Administrative Templates > Windows Components > Internet Explorer > Privacy.

    These two workarounds are recommended best practices and can prevent issues with redirection that situations other than private browsing can cause.

  • URL redirection does not work if a Windows 10 Universal app is the default handler for a protocol specified in a link. Universal applications, which are built on the Universal Windows Platform so that they can be downloaded to PCs, tablets, and phones, include the Microsoft Edge browser, Mail, Maps, Photos, Grove Music and others. Therefore, if you click a link for which one of these applications is the default handler, the URL will not be redirected. For example, if a user clicks an email link in an application and the default email application is the Mail universal app, the URL specified in the link will not be redirected.

    Workaround: Make a different application the default handler of the protocol of URLs that you want to redirect. For example, if Edge is the default browser, make Internet Explorer the default browser.

  • Machines that have secure boot enabled will leave the URL Content Redirection feature disabled. URLs cannot be redirected from these machines. URLs can, however, be redirected to these machines.