I use Norton Internet Security 2012, and would like to set the proxy server with a pac file. I created the pac file, and tried it with Microsoft Internet Explorer. It works fine. In NIS2012, I go to proxy server settings, put a tick to "Use automatic configuration script", and I set the URL as follows:
file://d:/proxy.pac
Behind a proxy server, I run live update, and it says "Unable to connect to the LiveUpdate server", like when I don't set the proxy server. When I connect to the internet directly, live update can connect.
In Windows I set full access to everyone on this file. I monitored the file with MS Process Monitor, but it's not accessed by any process. I monitored ccsvcsht.exe and it didnt try to find any "proxy.pac" file.
I think I tried everything in the NIS proxy server settings to make it work. If I set the proxy server manually, then LiveUpdate can connect. If i host the proxy.pac file on my local web server (IIS), and in NIS proxy server settings I set the URL: http://localhost/proxy.pac, then it works fine.
So the pac file is correct, but I suppose NIS ignores the "file://..." term.
I use Windows 7 Ultimate 64bit fresh install and NIS2012 19.5.0.145
Previously I tried it on Windows 7 Ultimate 32 bit with NIS2011 and NIS2012, and the problem was the same.
Thanks for the detailed information, I see it's a common problem with winhttp api. I'll write to the product suggestion topic, and ask for local pac file support or more proxy options.
I use Norton Internet Security 2012, and would like to set the proxy server with a pac file. I created the pac file, and tried it with Microsoft Internet Explorer. It works fine. In NIS2012, I go to proxy server settings, put a tick to "Use automatic configuration script", and I set the URL as follows:
file://d:/proxy.pac
Behind a proxy server, I run live update, and it says "Unable to connect to the LiveUpdate server", like when I don't set the proxy server. When I connect to the internet directly, live update can connect.
In Windows I set full access to everyone on this file. I monitored the file with MS Process Monitor, but it's not accessed by any process. I monitored ccsvcsht.exe and it didnt try to find any "proxy.pac" file.
I think I tried everything in the NIS proxy server settings to make it work. If I set the proxy server manually, then LiveUpdate can connect. If i host the proxy.pac file on my local web server (IIS), and in NIS proxy server settings I set the URL: http://localhost/proxy.pac, then it works fine.
So the pac file is correct, but I suppose NIS ignores the "file://..." term.
I use Windows 7 Ultimate 64bit fresh install and NIS2012 19.5.0.145
Previously I tried it on Windows 7 Ultimate 32 bit with NIS2011 and NIS2012, and the problem was the same.