URL Content Redirection is a feature already available in some other VDI solutions (e.g. Horizon).
This allows the VDI session to have URIs be openned not in the VDI session's browser, but instead in the browser on the client's machine. Examples of scenarios where this would be useful are if the website requires specific hardware (e.g. graphics cards, which often aren't financially viable on VDI solutions where most users don't have this need most of the time), or for cases where you don't want to enable web browsing from the VDI devices, to name just a couple.
Such functionality could be hacked up by writing a listener on the client machine which receives a URI and runs `Process.Start(new ProcessStartInfo { FileName = url, UseShellExecute = true });` to open it. On the VDI side we could set the "default browser" to an exe which accepts the URI as an argument, checks its domain, then for those we want to open on the client device (e.g. based on their domain) we connect to the client's listener and send the URI over to it. However, that's very basic / wouldn't be great from a security perspective (there being none), so having this integrated with the existing VDI solution where much of that functionality is already available & can be better controlled would be far preferable.
