Closed
Bug 105419
Opened 24 years ago
Closed 24 years ago
PAC: does not work when "Direct" is followed by proxy
Categories
(Core :: Networking, defect)
Tracking
()
People
(Reporter: Matthias.Morche, Assigned: neeti)
Details
(Keywords: testcase)
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:0.9.5) Gecko/20011011
BuildID: 2001101117
Proxy Autoconfiguration does not work, if there are patterns like:
if (dnsDomainIs(host, ".sat1.de"))
return "DIRECT; PROXY proxywww.sat1.de:8080";
If there is anything behind the "DIRECT" the nsProxyAutoConfig.js fails in line 95.
Reproducible: Always
Steps to Reproduce:
1. Setup a squid cache :-)
2. setup a proxy.pac, which contains
if (dnsDomainIs(host, ".mydomain.mycountry"))
return "DIRECT; PROXY mysquidcache.mydomain.mycountry:8080";
3. Surf to "http://myapache.mydomain.mycountry" using the above proxy.pac
Actual Results: You get a blank screen and an appropriate errormessage on the
javascript console (if open).
Expected Results: The addressed page has to pop up.
I believe that every platform suffers from this problem, if presented with.
Comment 2•24 years ago
|
||
bug 84798 covers failover (return "proxy1:port; proxy2:port; ...") not working.
When that's fixed, this should no longer break the parsing.
Your PAC still won't do anything -- "DIRECT" is always a valid proxy, so what
follows won't ever be used.
*** This bug has been marked as a duplicate of 84798 ***
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
VERIFIED, dupe.
Status: RESOLVED → VERIFIED
Keywords: testcase
QA Contact: benc → pacqa
Summary: Proxy Autoconfig does not work when "Direct" is followed by proxy → PAC: does not work when "Direct" is followed by proxy
You need to log in
before you can comment on or make changes to this bug.
Description
•