Closed
Bug 420093
Opened 17 years ago
Closed 9 years ago
Automatic proxy configuration URL bypasses localhost
Categories
(Core :: Networking, defect)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: pgpittman, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.12) Gecko/20080201 Firefox/2.0.0.12
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.12) Gecko/20080201 Firefox/2.0.0.12
When using the Automatic proxy configuration URL, there is no provision to bypass localhost (127.0.0.1) or any other IP address. If you type 127.0.0.1 in the address bar, Firefox ignores it and goes directly to the proxy server.
Reproducible: Always
Steps to Reproduce:
1. Enter a URL in Tools->Options->Advanced->Network->Automatic proxy configuration URL
2. Type http://127.0.0.1 in the address bar
3. Firefox goes directly to Proxy server URL
Actual Results:
Can't reach localhost
Expected Results:
Connected to localhost - not proxy server
Updated•17 years ago
|
Severity: major → normal
Component: General → Networking
Product: Firefox → Core
QA Contact: general → networking
Comment 1•17 years ago
|
||
That depend on your PAC file (the proxy configuration file stored at that location). Your system administrator can write a PAC file that forces every access to pass thru the proxy server (including 127.0.0.1), if there's a reason for it. That's the whole point of the PAC file.
You're assuming that I (or we, depending on the situation), can talk my (or our) ISP into altering/creating the PAC file. Firefox allows the abilit to exclude IP addresses if you use a manual setting but this doesn't allow for the use of a URL. Why not allow the same ability when using any other proxy setting?
-> new.
Thats a perfectly valid reason, I've been waiting for someone to mention it :)
I think Safari has this hardcoded... but I'd need to double check.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•