Closed Bug 683497 Opened 14 years ago Closed 14 years ago

Proxy: "No proxy for" does not support "192.168.1.*" anymore (only wildcard)

Categories

(Core :: Networking, defect)

6 Branch
x86_64
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: florianalbeck, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0.1) Gecko/20100101 Firefox/6.0.1 Build ID: 20110830092941 Steps to reproduce: I always had and networkrange in my lan for which connections i did not have to go throug a proxy. so i filterd this range with the "no proxy for" setting and typed 192.168.1.* to get all the lan clients. After updateing now to Firefox 6.0.1 ths wildcard doesn't work anymore. the no proxy setting only works if i specify the real ip adress like 192.168.1.5 or soemthing. then the proxy gets ignored, bit with the wildcard as 192.18.1.* firefox trys to establich the connection with the set proxy. Actual results: it dind't conect with the wildcard set, because firefox tired to get though proxy instead of ignoring it Expected results: ignore proxy, because wildcard was set.
Component: General → Networking
Product: Firefox → Core
QA Contact: general → networking
192.168.0.* doesn't work for me in FF3.6.20 and FF6 but 192.168.0.0/24 works as expected
Matti is right. Firefox doesn't use the wildcard syntax. The dialog box actually tells you what the syntax is. http://kb.mozillazine.org/No_proxy_for
Well...but I know for sure there was a time where such wildcards were supported...so I think it is quite stupid to remove such "features" silently... Ticket solved, thx... ;)
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → WONTFIX
(In reply to Florian Albeck from comment #3) > Well...but I know for sure there was a time where such wildcards were > supported...so I think it is quite stupid to remove such "features" > silently... > No, really, it never did. See for instance bug 242453 comment 10.
You need to log in before you can comment on or make changes to this bug.