User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.2; .NET CLR 1.1.4322; .NET CLR 2.0) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.7b) Gecko/20040316 With No Proxy For set to: 127.0.0.1,192.168.0.2,192.168.0.1,192.168.0.* When I browse 192.168.0.2, Mozilla still uses the proxy specified in Manual Proxy Connection HTTP Proxy. Reproducible: Always Steps to Reproduce: 1. Set No Proxy For to 127.0.0.1,192.168.0.2,192.168.0.1,192.168.0.* 2. Browse 192.168.0.2 Actual Results: Bad Request or other error messages Expected Results: Connected to the IP address without using the proxy specified in HTTP Proxy
bug 80918 again ? (might need to be reopened) In case you were surfing with a DNS-name (not 192.168.0.2), it's bug 136789.
What happens when you remove the wildcard (192.168.0.*) ? I'm thinking of bug 80918
(In reply to comment #2) > What happens when you remove the wildcard (192.168.0.*) ? I'm thinking of bug 80918 Actually even when the wildcard is removed, it doesn't work. I was using it without the wildcard, before I added the wildcard.
Wrong syntax: 127.0.0.1,192.168.0.2,192.168.0.1,192.168.0.* Correct syntax (removed redundant IPs): 127.0.0.1,192.168.0/24 127.0.0.1,192.168.0.0/24 see Bug 222127 and Bug 80918, and keep in mind bug 136789 Does it work now?
Yes, it works now... Please document the syntax required, such as 192.168.0/24
(In reply to comment #5) > Please document the syntax required, such as 192.168.0/24 That work will be done in Bug 222127. > Yes, it works now... So please resolve this bug as WORKSFORME.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → WORKSFORME
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.