Closed
Bug 190053
Opened 22 years ago
Closed 22 years ago
PAC: alternative connect methods not tried if proxy server not responding
Categories
(Core :: Networking, defect)
Tracking
()
People
(Reporter: puhuri+mozilla, Assigned: dougt)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020623 Debian/1.0.0-0.woody.1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020623 Debian/1.0.0-0.woody.1
If proxy autoconfiguration is configured to return multiple connect methods (as
described in page
http://wp.netscape.com/eng/mozilla/2.0/relnotes/demo/proxy-live.html), only the
first one proxy is tried. If it fails to respond, no other proxies are tried.
This bug is relaed to #79662
I'm not sure if functionality of mozilla is (or should be) superset of netscape
2.0. (i.e. is this a bug or feature request).
Reproducible: Always
Steps to Reproduce:
1.Create proxy autoconfiguration which returns string "PROXY localhost:65123;
DIRECT", assuming that you dont have any service on port 65123. Replace with
other port number if needed.
2.Try to connect any web site.
Actual Results:
I received "The connection was refused when attempting to connect
www.mozilla.org" error message even if www.mozilla.org would be reachable with
direct connection (with no proxy configured).
Expected Results:
It should have connected using direct connection instead of error message.
A proxy autoconfiguration file used:
function FindProxyForURL(url, host)
{
return "PROXY localhost:65123; DIRECT";
}
-> networking
Assignee: darin → dougt
Component: Networking: HTTP → Networking
QA Contact: httpqa → benc
Summary: alternative connect methods not tried if proxy server not responding → PAC: alternative connect methods not tried if proxy server not responding
Whiteboard: dupeme
(matti found it)
*** This bug has been marked as a duplicate of 84798 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
QA Contact: benc → pacqa
Resolution: --- → DUPLICATE
Whiteboard: dupeme
VERIFIED/dupe
This is fixed now, please try Mozilla 1.4b or later.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•