Yes, it is quite difficult to persuade Chrome to re-load a PAC file afresh. The Chromium "Net Internals" proxy configuration reporting page (whose URL SuperUser doesn't allow as a hyperlink), and its initialization reporting counterpart (likewise), are also useful: chrome://net-internals/nfigĬhrome://net-internals/proxyservice.init_log I diagnosed a syntax error in a fairly large PAC file with that, once.
Include more than just Chrome and Firefox in the mixture of Useful diagnosis tools, where "useful" incorporates "I've used them myself to diagnose problems.", include Chrome's JavaScript console and debug logging function. Welcome to the world of fun that is Proxy Auto-Configuration files (and indeed Google Chrome)! So my question is: how can I tell Chrome to reload the proxy.pac file, since that works for Firefox? (I thought I had solved the problem by saving the proxy.pac file locally, but apparently not). Eventually Chrome will pop up the proxy authentication dialog, but it can be hard to see (usually comes up in the wrong Spaces window, sometimes disappears straight away, can be buried under other application windows etc). I discovered by trial and error that in FireFox, if I go to the proxy settings, and press "reload" on the proxy configuration, then the problem goes away. I think this is related to the fact that the proxy requires username and password - perhaps it just discards unauthenticated requests or something. When reconnecting after a stint on the road, I often get a problem where pages simply don't load in Chrome or Firefox.
I frequently move my laptop (OSX) between different wifi areas, but my home base has an ethernet connection and relies on my organisation's proxy.pac file.
0 kommentar(er)
