201685 - Proxy: IPv6: add support in "No Proxy for "

Status: NEW

(Core :: Networking: Proxy, enhancement, P3)

Description

[Darin Fisher]

Support no-proxy-for IPv6 addresses.  this is a spin off from bug 80918, which
added code to store the no-proxy-for ip addresses in v6 format.  now all we need
to do is parse the no-proxy-for filter line for IPv6 address literals.  IPv6
address filters would have to be escaped in the usual []-escaping for IPv6
address literals (per RFC 2732).  for example, a filter like this should be
supported:

  [12AB:0:0:CD30::/60]:8080

Comment 1

[Denis Antrushin]

Attachment: simple fix

It looks like all we need here is to strip '[' and ']' surrounding IPv6 literal
string and everything will just work - rest of code is already IPv6 ready :-)
The only thing I'm not sure of is what the best way to trim first and last
characters from nsCAutoString. I used the following method:

+     if (host.get()[0] == '[') 		// IPv6 literal?
+	host.Trim("[]", PR_TRUE, PR_TRUE);

Also, I'm behind firewall that blocks CVS, so path is 'diff -c' (against v.1.50
of nsProtocolProxyService.cpp), not 'cvs diff', sorry.

Comment 2

[benc]

*** Bug 277378 has been marked as a duplicate of this bug. ***

Comment 3

[Hendrik Brummermann]

6 and a half years and its still not possible to use Firefox for IPv6 experiments inside a LAN. Sorry, for this spam, but this is really disappointing.

Comment 5

[u204240]

It looks like a duplicate of Bug 493483, which has been reported as FIXED.
But... Does the fix really work?  I don't think so.

Comment 6

[n3rd]

(In reply to comment #5)
> It looks like a duplicate of Bug 493483, which has been reported as FIXED.
> But... Does the fix really work?  I don't think so.

Yes, you are right. This fix for Bug 493483 does not work for IPv6 literals.
If I use the FQDN like www.kame.net in the exception list, the IPv6 (Firefox 4.0.1 and miredo on Linux 2.6; Only TCP is blocked here to force proxy usage (lame admins forgot UDP :-))) works correct, but when I use a prefix such as [2001::/16] it does not work.

Comment 7

[Masatoshi Kimura [:emk]]

What about [2001::]/16 ?

Comment 8

[Radek]

I want to connect to [::1], but it's made through proxy. Setting "::1" or "[::1]" in exclude doesn't resolves problem. Firefox 8.0

Comment 9

[adrian]

holy ****, this is a long time.  browser on my phone does this correctly, but not firefox?  not even with an extension??

Comment 10

[Firefox Bug Husbandry Bot]

Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258

Comment 11

[Firefox Bug Husbandry Bot]

Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258

Comment 12

[Jens Stutte [:jstutte]]

Bulk-downgrade of unassigned, >=3 years untouched DOM/Storage bug's priority.

If you have reason to believe this is wrong, please write a comment and ni :jstutte.

Comment 13

[BMO Automation]

Moving bug to Core/Networking: Proxy.

Comment 15

[ipv6only]

Issue is still present in 2024. Firefox version is 115.12.0esr (64-bit) from Debian.

On 2024-07-04, my ISP (Tele Columbus) disabled IPv4 on my cable connection. This makes me one of the first people to have IPv6-only internet at home.

Unfortunately, there are still too many websites that still lack IPv6 in 2024 (such as THIS bug tracker). So I was forced to configure Firefox to use a proxy for IPv4.

This didn't work as expected: Although I can now access IPv4 sites again, all of my web traffic - including IPv6 sites - is now going through the proxy. The exception I configured for range ::/0 is simply ignored.

Comment 16

[Valentin Gosu [:valentin] (he/him)]

Looking at the code, this should already be supported, but note the syntax.

https://searchfox.org/mozilla-central/rev/1a7d78fdc729359ea43c65d647879c32bcdfb852/netwerk/test/gtest/TestProtocolProxyService.cpp#101-102

"example.com, 1.2.3.4/16, [2001::1], 10.0.0.0/8, 2.3.0.0/16:7777, [abcd::1]/64:123, *.test.com";

The problem with bug 1906511 is that it attempts to filter out all IPv6 addresses ::/0, [::]/0 which I don't think works because all of the filters are actually stored as IPv6 addresses.