From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.8) Gecko/20020204 BuildID: 2002020406 Unlike pre 6.x versions of Navigator, when auto proxy configuration URL is selected, and user is not on work VPN network, pages do not load. Behavior should be that when proxy's presence is not detected (user connected directly to Internet, not VPN) pages will load. Reproducible: Always Steps to Reproduce: 1.configure automatic proxy URL 2.connect only to ISP, not to VPN associated with proxy server 3.pages will not load because browser wants to detect proxy server 4. have to select direct connection to internet and reload browser when not on VPN. Actual Results: Pages do not load. Expected Results: Pages should load.

+qawanted - dupeme. PAC has nothing to do with this. We have problem with changing network interfaces in a single mozilla session. If you can run PAC-less for a while and connect to the VPN (maybe to a test host), you will find you have the same problem.

Temporarily "futuring" all PAC&SOCKS bugs to clear new-networking queue. I will review later. (I promise) If you object, and can make a case for a mozilla 1.0 fix, please reset milestone to "--" or email me.

More specific information is needed here, but I think what you are really saying is that: You have a PAC specified that is VPN-only, and you expect mozilla to kind of flip to direct-only when it isn't on the VPN (and by effect, fails to load the PAC file). What is the comparable 4xp behavior?

partial summary cleanup.

reporter, is an error returned if PAC tries to send you to a non-existent proxy? I need more information if this is going to be fixed.

4xp - in bug 79662 comment 1, I said this works in 4xp.

sounds related to PAC failover.

marking as dependent on bug 84798.

Does this bug still occur with Firefox 1.5 or later?

-> reassign to default owner

Dropping qawanted due to lack of activity. Please re-add if you can reproduce this on latest nightly and need anything from QA.