Closed Bug 602016 Opened 15 years ago Closed 9 years ago

Use System Proxy Setting does not respect CIDR notation in Bypass Settings

Categories

(Core :: Networking, defect)

Product:
Core
Component:
Networking
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
major

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1233360

People

(Reporter: apple4ever, Assigned: xeonchen)

Details

(Whiteboard: [necko-active][proxy])

User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0b7pre) Gecko/20101004 Firefox/4.0b7pre Build Identifier: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0b7pre) Gecko/20101004 Firefox/4.0b7pre We have our network configured to use a proxy server(192.168.10.1) that also connects to an authentication server (192.168.10.2). We have Firefox set to use the system proxy settings. In the bypass proxy settings we have *.somewhere.com and 192.168/16. When the proxy server attempts to redirect the connection to the authentication error, Firefox is still attempting to go through the proxy server for that connection (which fails). Reproducible: Always Steps to Reproduce: 1. Setup a proxy server, and block all connections outbound except for ones from that proxy server. 2. On a Mac, in System Preferences, under the Network Pane, click Advanced. Set the proxy server up, and under the Bypass proxy settings at the bottom, put in 72.14/16 (72.14.0.0/16 also is acceptable) 3. Go to 72.14.204.147 (its Google.com) Actual Results: The Google.com homepage showed up Expected Results: The connection should have been refused if Firefox was attempting to connect directly because all direct connections are refused. Instead, its going through the proxy server because the connection was not refused. I have tested this on 3.5.7 to 4.0B7
Also, I understand that 172.19.0.0/16 is the preferred format for Firefox, and that 172.19/16 is not supported. But Apple has that as a standard default in their bypass settings, and OS X supports that format, so Firefox should as well. Regardless, 172.19.0.0/16 is still not pulled in by Firefox (though oddly enough 172.19.* is, which I also believe is unsupported).
see also bug 470207
Component: Preferences → Networking
Product: Firefox → Core
QA Contact: preferences → networking
Version: unspecified → Trunk
Whiteboard: [necko-backlog]
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
The statement is quite clear that the issue has been fixed in bug 1233360.
Assignee: nobody → xeonchen
Whiteboard: [necko-backlog] → [necko-active][proxy]
You need to log in before you can comment on or make changes to this bug.