Symptoms

When the user configures view_proxy in iApp using "If external clients use a network translated address to access View, what is the public-facing IP address?" (or) In VPE using variable assign, APM VMware VDI does not consider this value in patching PCoIP connection. It only finds the Host Header value or virtual server IP address.

Impact

In some network deployments, the user will not be able to open a PCoIP connection to the desktop/app.

Conditions

This issue is seen when: 1. The view_proxy is configured. 2. PCoIP is used to connect to a desktop/app.

Workaround

When HTTP_REQUEST { if { [HTTP::uri] contains "/broker/xml" } { set jsid [HTTP::cookie value JSESSIONID] if { $jsid != "" } { set ctype [ACCESS::session data get -sid $jsid session.client.type] if { $ctype != "" && $ctype == "apm-webtop" } { set vproxy [ACCESS::session data get -sid $jsid view.proxy_addr] set old_host [HTTP::host] if { $vproxy != "" && $old_host != "" && $vproxy != $old_host } { HTTP::header replace "Host" $vproxy log local0. "Replaced - jsid = $jsid vproxy = $vproxy host = $old_host" } } } } }

Fix Information

APM VMware VDI should use the view_proxy address instead of the host header.

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips