297505 - wpad doesn't support multple PROXY definitions

Status: RESOLVED WORKSFORME

(Core :: Networking, defect)

Description

[Jason Haar]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4

According to the Netscape Navigator Proxy Auto-Config File Format
(http://wp.netscape.com/eng/mozilla/2.0/relnotes/demo/proxy-live.html), you are
allowed to enter multiple PROXY definitions to handle the case of primary
servers failing.

e.g.

return "PROXY h1:3128; PROXY h2:3128";

Well I've incorporated that into our WPAD file, and now Internet Explorer is
working perfectly (turn off first proxy (h1), IE hangs for 30 secs then starts
calling second proxy (h2)), but Firefox 1.0.4 under WinXP refuses to do the
same. It continually calls the first server, until it times out after a minute
or so.

Even restarting FF doesn't help - it is unable to use the network until the
first proxy is brought back up.

This seems to imply FF throws away the other PROXY references - only seeing the
first?

I have emulated this by having two Linux Squid proxies, and using iptables to
DENY port 3128 connections from the client. This means the TCP transaction times
out instead of getting a "CONNECTION REFUSED" style error. It better emulates a
n OS crash or host outage rather than a service outage.


Reproducible: Always

Comment 1

[Christian :Biesinger (don't email me, ping me on IRC)]

that should work... or was it only fixed after 1.0.x? Does it work in deer park
alpha 1?

Comment 2

[Adam Guthrie]

Download the latest trunk and see if you can reproduce it?
http://stage.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/

Comment 3

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 4

[Jason Haar]

(In reply to comment #2)
> Download the latest trunk and see if you can reproduce it?
> http://stage.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/

It's 3 months since I reported this, and it's still a problem. I just tried it
with Firefox 1.0.7 (and Mozilla 1.7.12) with a PAC file ending in

return "PROXY h1:3128; PROXY h2:3128";

If h1 is offline, Firefox and Mozilla won't try h2. They just error saying

The operation timed out when attempting to contact www.google.com



Internet Explorer will BTW. It hangs for 20+ secs, then jumps over to the 2nd proxy.

Jason

Comment 5

[Darin Fisher]

Jason: Can you please test Firefox 1.5 beta 1?

http://www.mozilla.org/projects/firefox/

Thanks!

Comment 6

[Jason Haar]

(In reply to comment #5)
> Jason: Can you please test Firefox 1.5 beta 1?
> 
> http://www.mozilla.org/projects/firefox/
> 
> Thanks!

Sweeeeeet!

That fixed it. 

You may close this bug report now I suppose! :-)

Comment 7

[Darin Fisher]

WORKSFORME w/ FF 1.5b1

Comment 8

[benc]

Does this have anything to do w/ the wpad implementation? It seems like a PAC
only problem.