The URL Content Redirection feature supports redirection from a remote desktop or published application to a client, and from a client to a remote desktop or published application.

Redirection from a remote desktop or published application to a client is called agent-to-client redirection. Redirection from a client to a remote desktop or published application is called client-to-agent redirection.

You might want to set up the URL Content Redirection feature for security purposes. For example, if an end user clicks a link in their client browser that points to a URL outside your company network, that link might be opened more securely in a published application. With client-to-agent redirection, you can designate a certain published application to open the link from the client.

Agent-to-client redirection
With agent-to-client redirection, Horizon Agent sends the URL to Horizon Client, which opens the default application for the protocol in the URL on the client machine.

For the list of browsers that support agent-to-client redirection, see the “Web browsers for Windows agents” section under System Requirements for URL Content Redirection.

Client-to-agent redirection
With client-to-agent redirection, Horizon Client opens a remote desktop or published application that you specify to handle the URL. If the URL is redirected to a remote desktop, the link is opened in the default browser for the protocol on the desktop. If the URL is redirected to a published application, the link is opened by the specified published application. The end user must be entitled to the desktop or application pool.

For the list of browsers that support client-to-agent redirection, see the sections for platform-specific clients under System Requirements for URL Content Redirection.

You can redirect some URLs from a remote desktop or published application to a client, and redirect other URLs from a client to a remote desktop or published application. You can redirect any number of protocols, including HTTP, HTTPS, mailto, and callto. The callto protocol is not supported for redirection with the Chrome browser. You can also specify which applications are supported for the protocol in the URL.