Closed
Bug 139967
Opened 23 years ago
Closed 22 years ago
Proxy/IPv6: Host line
Categories
(Core :: Networking, defect)
Core
Networking
Tracking
()
RESOLVED
WORKSFORME
Future
People
(Reporter: dima, Unassigned)
References
(Blocks 1 open bug)
Details
when you do something like http://[3ffe:8210:f000:f::1]/ and mozilla tries to do
it through a proxy, which doesn't seem to support ipv6 or something, mozilla end
up with a blank page w/o any notification of an error.
moreover if you try to "view source" of this blank page it pups up wird dialogs
like "would you like to save file of type #1 [#2]".
here's what goes on, as seen with tcpdump -s 2000 -w /tmp/blah host <this> and
host <proxy>
mozilla:
GET http://[3ffe:8210:f000:f::1]/ HTTP/1.1^M
Host: [3ffe:8210:f000:f::1]^M
User-Agent: Mozilla/5.0 yada yada yada
proxy:
HTTP/1.0 400 Invalid header received from browser
-> NEW
Looks real to me, but I don't know what an IPv4 based proxy is going to do here...
Severity: enhancement → major
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Linux → All
Hardware: PC → All
Summary: mozilla doesn't present browser responce → Proxy/IPv6: Host line
|
||
Comment 2•23 years ago
|
||
reducing severity because i don't see how we can successfully load a website
from an IPv6 address literal via a proxy that doesn't understant IPv6 address
literals.
it would seem that what we need to do is simply improve on the error handling.
reporter: can you confirm that the proxy server in question doesn't support IPv6
address literals?
Severity: major → minor
Target Milestone: --- → Future
|
|
||
Comment 4•23 years ago
|
||
benc: the addressing looks correct to me.
|
Reporter | |
Comment 5•23 years ago
|
||
no, proxy doesn't support ipv6 address in the url, like follows:
#> telnet www-cache 8080
Trying xx.xx.xx.xx
Connected to www-cache.xx.xx.xx.
Escape character is '^]'.
GET http://[::1]/ HTTP/1.0
HOST 1.1.1.1
HTTP/1.0 400 Bad Request
Server: Squid/2.4.STABLE6
Mime-Version: 1.0
Date: Fri, 26 Apr 2002 10:02:05 GMT
Content-Type: text/html
Content-Length: 846
Expires: Fri, 26 Apr 2002 10:02:05 GMT
X-Squid-Error: ERR_INVALID_URL 0
X-Cache: MISS from www-cache.xx.xx.xx.
Proxy-Connection: close
<HTML><HEAD>
<TITLE>ERROR: The requested URL could not be retrieved</TITLE>
</HEAD><BODY>
<H1>ERROR</H1>
<H2>The requested URL could not be retrieved</H2>
<HR>
<P>
While trying to retrieve the URL:
<A HREF="http://[::1]/">http://[::1]/</A>
<P>
The following error was encountered:
<UL>
<LI>
<STRONG>
Invalid URL
</STRONG>
</UL>
---
still trying to "view source" on the blank page mozilla end up with is
definitely buggy, though I think I should file that as a separate bug, if
it isn't exactly what 92553 or similar are.
|
||
Comment 6•22 years ago
|
||
I just tried this with Mozilla from the 1.0 branch and it nicely shows the
Invalid URL page that squid server spits out.
|
||
Comment 7•22 years ago
|
||
I have the same problem (I'm running Mozilla/5.0 (X11; U; FreeBSD i386; en-US;
rv:1.3) Gecko/20030404), but it also affects any host that has an AAAA record.
In my network environment, IPv4 address must go through the proxy (I don't use
NAT) but IPv6 is routable (give or take firewall rules). What I would like to
see is a checkbox in the proxy config window to disable proxies for all IPv6
addresses. I think that would be a natural fit with bug 201685. Of course this
won't help with the error handling issue.
|
|
||
Comment 8•22 years ago
|
||
i just tested a trunk build against a squid proxy server (which doesn't
understand IPv6 address literals). it gave me an error page, so i think this
bug can be closed WFM.
stacy: sounds like you might want to file a new feature request (RFE) bug report.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•