One of our customers is using the Client Proxy Autoconfig Script feature in a Network Access profile to send a PAC file to a Edge client.
This PAC file is configured as Hosted Content on the F5 and a user has access based on a existing session.
When the Edge clients makes a connection, we can see this URL being send to the client, but when the Edge clients wants to get the PAC file, it connects to the IP-address and the the hostname.
Because the virtual server has a SSL certificate, the connection fails and the Edge client cannot get the PAC file from the F5.
F5 version is: 184.108.40.206 005
Did we missed something here? Why is the Edge client connecting on IP and not on hostname?