Closed
Bug 248476
Opened 20 years ago
Closed 20 years ago
"no proxy for" setting does take ip range
Categories
(Firefox :: Settings UI, defect)
Tracking
()
VERIFIED
DUPLICATE
of bug 222127
People
(Reporter: tony_petruzzi, Assigned: bugzilla)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040614 Firefox/0.9
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040614 Firefox/0.9
When entering an ip range for exclusion, such as 10.* or 10.*.*.*, Firefox still
hits the proxy server. I have tried mulitple combinations to exclude the 10
range of our network such as: 10.*; 10.*.*.*; 10.230.100.*; 10.230.*.* and
nothing seems to work. I have seen another bug report: 238262, that states it
doesn't work if enter the ip range and a port. I'm not entering a port.
Reproducible: Always
Steps to Reproduce:
1.see details
Actual Results:
I get the proxy login box.
Expected Results:
It should have by passed the proxy and gone directly to the address
none
Comment 1•20 years ago
|
||
You want something like 192.168.1.0/24
or, in your case, 10.0.0.0/8
duping to the bug that'll show the format in the dialog.
*** This bug has been marked as a duplicate of 222127 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Yeah, IP ranges are only supported in a special format of ipaddr[/mask], see Bug
80918.
Examples for the private IP ranges:
10.* doesn't work, you have to use 10.0/8, 127.* == 127.0/8, 192.168.* ==
192.168/16, 172.xx.* (with xx = 16-31) == 172.16/12
In case you were surfing with a DNS-name (not an IP directly), it's bug 136789.
General bug for better wildcard support is Bug 48718.
You need to log in
before you can comment on or make changes to this bug.
Description
•