Open
Bug 201685
Opened 21 years ago
Updated 2 months ago
Proxy: IPv6: add support in "No Proxy for "
Categories
(Core :: Networking: Proxy, enhancement, P5)
Core
Networking: Proxy
Tracking
()
NEW
People
(Reporter: darin.moz, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [IPV6][necko-backlog])
Attachments
(1 file)
2.38 KB,
patch
|
Details | Diff | Splinter Review |
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
Reporter | ||
Updated•21 years ago
|
Comment 1•21 years ago
|
||
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.
Summary: Support no-proxy-for IPv6 addresses → Proxy: IPv6: add support in "No Proxy"
Summary: Proxy: IPv6: add support in "No Proxy" → Proxy: IPv6: add support in "No Proxy for "
*** Bug 277378 has been marked as a duplicate of this bug. ***
Reporter | ||
Updated•18 years ago
|
Assignee: darin → nobody
Status: ASSIGNED → NEW
QA Contact: benc → networking
Target Milestone: Future → ---
Comment 3•15 years ago
|
||
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.
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.
(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•13 years ago
|
||
What about [2001::]/16 ?
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
holy ****, this is a long time. browser on my phone does this correctly, but not firefox? not even with an extension??
Updated•10 years ago
|
Whiteboard: [IPV6]
Updated•8 years ago
|
Whiteboard: [IPV6] → [IPV6][necko-backlog]
Comment 10•7 years ago
|
||
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P1
Comment 11•7 years ago
|
||
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: P1 → P3
Comment 12•3 years ago
|
||
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.
Severity: normal → S4
Priority: P3 → P5
Comment 13•2 months ago
|
||
Moving bug to Core/Networking: Proxy.
Component: Networking → Networking: Proxy
You need to log in
before you can comment on or make changes to this bug.
Description
•