We are attempting use a proxy.pac file on our Windows 2003 web server to limit what web sites can be accessed from some public library computers. Here is an example of the proxy.pac file:
function FindProxyForURL(url, host)
if (isPlainHostName(host) ||
dnsDomainIs(host, ".learnatest.com") ||
return "PROXY alert.owls.lib.wi.us"
We have configured IIS on our Server 2003 web server to use a MIME type "Assosiated Extension: .pac" with a "Content Type(MIME): application/x-ns-proxy-aut
We have also configured IE 6.0 to "Use automatic configuration script" which points to the URL location of our proxy.pac file.
At first our tests looked very good, but we have found an odd problem. First of all, we can access the 3 URLs listed in the proxy.pac file with out any issues, good. And if we try to access, for example, http://www.symantec.com
, the browser comes back with our custom "sorry you can't get there from here" page. So far so good as this is what we would expect.
But the problem is if we try to go to a Web site's subdirectory, for example, http://www.symantec.com/avcenter
, the browser comes back with a "Page Cannot Be Found" 404 error. This pattern is very consistant and happens with all Web site subdirectorys not listed in the proxy.pac file (not just symantec's) We would like these subdirectory web site visits to also return our "sorry" page which is much kinder than a general 404 error.
Can anyone see a problem in our proxy.pac file? Or am I missing a step with this type of configuration?
Thank you in advance for your help,
Computer Network Manager
Outagamie Waupaca Library System