115948 - Proxy: "no proxy for" should support subnets based on ip?

Status: RESOLVED DUPLICATE of bug 91587

(Core :: Networking, defect)

Description

[Terry Davis]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.6) Gecko/20011120
BuildID:    

There is an option that says bypass "no proxy for".  This expects domains.  What
if I am on a local subnet that uses hostnames only?  This would imply that I
would need my browser to look at my subnet and filter based on that.  Internet
Explorer does this.
Example:  if I had birddog.com in my "no proxy for", then "www.birddog.com"
would not be sent through the proxy, but "www" would.

Reproducible: Always
Steps to Reproduce:
Enter domain for proxy filter

Actual Results:  hostnames still get proxied.

Expected Results:  bypassed proxy for local hostnames

Comment 1

[sairuh (rarely reading bugmail)]

networking?

Comment 2

[Terry Davis]

Are you requesting something from me?
Thank you!

Comment 3

[benc]

->NEW

cleaned up front of summary.

This is might be the duplicate of several different bugs.

I think what is being said here is:

my default domain is birddog.com, and I have it in "no proxy for".

"www.birddog.com" is not proxied (good)
"www" is proxied, (which eventually tries to connect to www.birddog.com, which
not what I want (bad))

Probably you are saying that you like the microsoft feature, and so you want bug
72444. If you look in that bug, you can see that we are stuck trying to
understand the underlying behavior.

Or, you might be saying that we should offer a simple "no-proxy hostname" option
(a simpler version of bug 72444). The underlying problems is that the current
"no proxy" is basically a string filter of the hostname, without having a robust
understanding of DNS and hostname syntax. PAC files have been used to provide
better "no proxy" implementations.

Or, you might be saying that after resolving to an IP, we do a subnet mask of
the destination to see if is on the local network (I'm not sure if we can do
this easily...)

(Interestingly enough, bug 88217, and RFE for a preference to make all hostnames
into FQDN's in DNS would also make this problem go away...) 

Comment 4

[Olav Vitters]

summary seems to suggest dupe of bug 80918

Comment 5

[Doug Turner (:dougt)]

yup.  this is a subset of the work needed for 80918.

*** This bug has been marked as a duplicate of 80918 ***

Comment 6

[benc]

Tha summary change was made by me. I still don't think we know what the reporter
really wants...

Comment 7

[benc]

V/dupe.

Comment 8

[benc]

REOPEN:
bah. this was about hostnames, which is still unfixed.. I will dupe later.

Comment 9

[benc]

*** This bug has been marked as a duplicate of 91587 ***