239260 - No Proxy For doesn't work with IP addresses if I key in IP addresses, and browse web sites using IP addresses

Status: VERIFIED WORKSFORME

(Core :: Networking, defect)

Description

[Chua Chee Wee]

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

Comment 1

[Jo Hermans]

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.

Comment 2

[Olivier Cahagne]

What happens when you remove the wildcard (192.168.0.*) ? I'm thinking of bug 80918

Comment 3

[Chua Chee Wee]

(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.

Comment 4

[OstGote!]

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?

Comment 5

[Chua Chee Wee]

Yes, it works now...
Please document the syntax required, such as 192.168.0/24

Comment 6

[OstGote!]

(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.

Comment 7

[benc]

V/wfm.