Hey all , I’ve been using a very basic Auto Configuration script file (proxy.pac) file for a little over a year now , but something isn’t working with Firefox and OpenSuse 11.0
I have the .pac file saved in /home/user/bin/proxy.pac
This same file works great on my Windows machine and has also worked on previous linux machines. But not today.
It’s my understanding that Firefox needs file://<path to file>
So am I correct in using the 3 slash format ?
**
file:///home/user/bin/proxy.pac**
I feel like I remember this issue a year ago when I first did this on SLED 10.3 Is there some quotes I’m missing or something else ?
facts:
No error, it just times out as if the proxy is not being set when reading the script.
Manual proxy works fine in firefox
IP address and Subnet match the proxy.pac requirements
Manual proxy is setup in Yast proxy settings and is working fine.
PAC files need to be served by a web server as the MIME type is application/ns-proxy-autoconfig (or something similar, too lazy to go check). Using a file might have worked in the past, I seem to recall I did it once, but Mozilla may have revoked that latitude now.
Looking through some of the settings , I noticed the “Network Proxy” option in the control center. It offers a script file option , but is currently set to " Use system proxy "
The issue with that is that the system Proxy in Yast does not offer the script option.
Does this mean that perhaps setting this Script path in the Control panel " Network Proxy " option , then it may make a difference ?
Looks fine to me. No idea what’s wrong. Not important now, but if this is a non-portable machine, when would you ever use DIRECT? You would always use the proxy on your LAN right?
No it’s a Novell Bordermanager Proxy (Authentication disabled) that works with a manual setting in the Proxy fields, it just doesn’t seem to be reading the script at all.
Does the script name end in .pac? If it ends in something else the browser might be trying to download it instead of reading it. This doesn’t happen with PAC files served by a web server because the MIME type is sent along, but with a file:// resource, it has to guess from the filename.
I don’t have a server to store it on , unless I can talk my boss into letting me store it on the same server as our Corporate .pac file. Which I doubt since it’s mainly for personal use.