207633 - PAC: Failover UI and proxy availability cache

Status: VERIFIED DUPLICATE of bug 224237

(Core :: Networking, defect)

Description

[benc]

(broken off from bug 84798)

http://home.netscape.com/eng/mozilla/2.0/relnotes/demo/proxy-live.html 

If there are multiple semicolon-separated settings, the left-most setting will
be used, until the Navigator fails to establish the connection to the proxy. In
that case the next value will be used, etc.

The Navigator will automatically retry a previously unresponsive proxy after 30
minutes, then after 1 hour from the previous try (always adding an extra 30
minutes). 

If all proxies are down, and there was no DIRECT option specified, the Navigator
will ask if proxies should be temporarily ignored, and direct connections
attempted. The Navigator will
ask if proxies should be retried after 20 minutes has passed (then the next time
40 minutes from the previous question, always adding 20 minutes).
--
Our current failover mechanism works but peformance would probably be better if
we remembered the down proxy and left it alone, rather than retrying it all the
time.

I've only looked at a connecction refused (RST) testcase, but connecction
establishment timeout could be slow.

Comment 1

[Maarten Geurts]

Current PAC failover fails for firefox 0.9.2 win32

returned is:
	{
	return "PROXY 144.44.35.75:80; PROXY 144.44.238.151:80";
	}
first host is completely down. (no ping, no hostname).

error message is "the operation timed out when trying to connect www.google.com"
status bar stows "timed out" 

Expected behavior in my opinion: second proxy is tried after the first has a
timeout an is reused for the next 20 minutes. 

So it is not only the UI that could use improvement. 

Comment 2

[Darin Fisher]

This is fixed on the trunk (please try Mozilla 1.8 alpha 2).

*** This bug has been marked as a duplicate of 224237 ***

Comment 3

[benc]

V/dupe.
NOTE: The implementation is not exactly the same as the spec.

Comment 4

[Oliver]

Hi,

I see exactly this problem again in version 66.0.4. It was "reintroduced" in Version 65.0.0. So far, I did not roll out Versions higher than 64.0.2 (last version that works). But now I have to use newer versions because of the "AddOn issuer"... :(

Can you please look into this?

Thanks,

• Oliver

Comment 5

[Oliver]

Forgot to mention:

If I set this proxy.pac as "System Proxy" I see the same behavior in Firefox. But other Browser (Explorer and Chrome) work fine and fast with that .pac file.