User navigates to a webpage whitelisted in the Studio Policy Browser Content Redirection ACL Configuration.
VDA remotes IE 11 Web Browser instance to Receiver via Thinwire. This feature is an extension of existing HTML5 Video Redirection components to add support for entire-browser-content redirection, instead of replacing a single video. It is able to manipulate the browser in a way that can intercept page loads, inject our script, monitor for changes to browsing history, and amend it to match the client side. The most-noticed and complained-about site is YouTube, which is particularly hostile to our HTML5 Video Redirection feature, as it does complicated JavaScript processing and uses MSE extensively. Sites may eventually incorporate Encrypted Media Extensions (EME), also, which could further complicate video redirection efforts. These can be handled by the HTML5 Video Redirection feature, except that it does not yet handle videos streamed using Media Source Extensions (MSE). Most problematic are sites incorporating HTML5 video elements. We see very high CPU utilization caused by web browsing on the VDA side. Why is Browser Content Redirection Required? It will utilize endpoint CPU, GPU and RAM resources and will not require any graphics, video, or animation to be rendered over Thinwire. The browser runs on the endpoint device instead of on the VDA. Browser on the VDA: Internet Explorer 11 (this is the only supported browser and version)īrowser Content Redirection prevents the execution/rendering of web pages on the VDA side by creating a corresponding browser instantiated by Receiver that will be responsible for rendering the URL. #REDIRECTOR EXE CITRIX WINDOWS#
VDA operating system: Windows 10, Windows Server 2012 R2, Windows Server 2016.Citrix Receiver for Linux 13.9 or higher.Citrix Receiver for Windows 4.10 or higher.
Windows 7, 8.x,or 10, and Internet Explorer 11.
0 kommentar(er)
