WPAD.DAT - Printable Version +- Wight Support Forum (http://wightsupport.com/forum) +-- Forum: Wightsupport Forums (http://wightsupport.com/forum/forumdisplay.php?fid=1) +--- Forum: Proxy (http://wightsupport.com/forum/forumdisplay.php?fid=22) +--- Thread: WPAD.DAT (/showthread.php?tid=24) |
WPAD.DAT - wightsupport - 21-06-2017 Using wpad.dat negates the need to type proxy settings directly into a browser. It also allows continued use of the Internet away from site as it looks to see if you are connected either to a specific domain or IP range. There are three stages to making this work. Stage 1 - IIS Settings Since the web browser is trying to fetch the configuration file (wpad.dat) by using the HTTP protocol, the hosting server should be able to do so. The hosting web server must be also set to serve .dat files as “application/x-ns-proxy-autoconfig” mime types and the wpad.dat file should be located at the web site’s root directory. For example in an IIS configuration, you should do the following:
{ //Ok so this bit ensures that any local domains don't go out via a Proxy if (shExpMatch(host,"*.stmarys.local")) { return "DIRECT"; } //This bit makes sure that devices such as printers can be accessed if they are on the local IP range if (isInNet(host, "10.17.81.0", "255.255.255.0")) { return "DIRECT"; } //Finally after the exclusions we can send all traffic via a proxy. return "PROXY surfprotect.exa-networks.co.uk:3128; DIRECT"; } The narrative is self explanatory for the exceptions (DIRECT) commands. The proxy settings can be changed to suit the environment. For example RM uses segfl.ifl.net:8080 Stage 3 - Add it to either DNS or DHCP
Credit WPAD.DAT |