From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.0) Gecko/20020530 BuildID: Mozilla 1.1a+ Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1a+) Gecko/20020626 Our proxy autoconfig file works well with IE 6.0 and Netscape 4.79. Netscape 4.79 unfortunately takes about 35 seconds before it redirects anything, versus about 2 seconds for IE 6. Our pac file directs http, https, ftp and socks client traffic to different DNS names for the proxy servers. Two proxy servers are provided in the pac file for each type of client traffic. The main reason this was done (aside from redundancy) was to separate ftp traffic to a different port to allow low prioritization of this traffic as it passes over our WAN. Mozilla 1.0 and 1.1A+ (20020626) has a bug with auto configuration fail over - it doesn't do it at all. If the primary proxy becomes unavailable, Mozilla 1.0 exhibits the following message: "The connection was refused when attempting to contact www.mozilla.org" If the primary proxy is restarted, Mozilla responds properly again. Also, is there a prefs.js setting to reduce the Netscape/Mozilla timeout before trying the secondary proxy server? If not, this would be a very desirable feature, because IE 6 cuts over to the alternate proxy so quickly relative to Netscape 4.79. The default proxy wait value should be at most 3 seconds before the alternate proxy server is tried. Reproducible: Always Steps to Reproduce: 1. Start Mozilla on an internal network client using a proxy auto configuration file. 2. Respond to the LDAP challenge to view an external Internet web site. 3. Turn off default proxy while leaving secondary online 4. Try browsing anywhere externally - the error message "The connection was refused when attempting to contact www.mozilla.org" (or whatever site you are viewing) results. 5. Turn primary proxy back on 6. Browsing continues normally Actual Results: The error message "The connection was refused when attempting to contact www.mozilla.org" (or whatever site you are viewing) results. Expected Results: Mozilla should detect no response from the primary proxy server, retrieve the secondary proxy listred in the pac file and attempt to use the secondary proxy.

PAC fallover isn't implemented yet *** This bug has been marked as a duplicate of 84798 ***

VERIFIED, same problem.