Normal 0 false false false EN-US X-NONE X-NONE
My customer wants to host the PAC file on a web server in their DMZ, so it is visible both internally and externally. We are using split-horizon DNS with a domain name owned by the customer. This functions well, and we have a working PAC file.
The problem we have is when using the Websense endpoint, it ignores the location of the PAC file that we specify, and points all browsers to the Websense-hosted PAC file (eg http://hybrid-web.global.blackspider.com:8082/proxy.pac?p=xxxxxxx).
The Websense-hosted PAC file is not visible from the customer's internal networks, and will prevent the endpoint devices from roaming freely between internal and external networks. Their security policy forbids granting all internal clients to access the Websense-hosted PAC file through the firewall (for obvious reasons).
Is there any way of forcing the Websense endpoint to use a PAC file that is not hosted by Websense?