I recently had a similar experience.
Don't ask me why, but for some reason, the name "proxy.pac" does not work for me when used on a local drive. Try renaming to proxy.txt and use the syntax:
Also, you can host the pac on the gateway as well.
Activate the File Server:
Upload the file:
Set your browser:
Both suggestions are good advice, I would also add:
1) Uncheck automatically detect settings
2) Make sure you are saving in ANSI with notepad as IE can be funny about encodings, UTF8 in particular is a problem with IE6.
The last time I saw an issue with proxy.pac locally it was actually local security blocking it as highly suspicious behavior.
This actually fixed it for me, too.
I had to save with Notepad to ANSI, and file://c:/proxy.pac started working on my local drive.
Good job, Chris.
Thank you so much for the help eelsasser! Your configuration worked like a charm, just like I was expecting. The only question I have for you now is how do you access the web gateway once those settings are in place? Do you have a PC outside of those settings or did you figure out a way to do it while still having those applied to your PC? I've tried most things I can think of but still can't get access....
While that PAC file you are using might be ok for testing, it is not complete for a production system. You must write is so there are exclusions for hosts on your local network.
Attached is a doc about PAC files. I wrote it for MWG6, but the PAC file itself remains the same. Use some of the snippets in there to exclude around your local subnets and internal domains.
Wow, that document is exactly what I was looking for! You saved me from having to Google all the domain specific commands I knew I was going to need. Just didn't realize accessing the Web Gateway would be part of that as well. Thank you so much for all your help!
Yeah, trying to proxy the GUI through itself is a challenge. Especially since I restrict only to port 80 and 443 on mine, so the 4711/4712 ports don't go through at all.