My favorites | Sign in
Logo
             
New issue | Search
for
| Advanced search | Search tips
Issue 1726: IPv6 support needed
2 people starred this issue and may be notified of changes. Back to list
 
Reported by johan.denoyer, Sep 07, 2008
Product Version      : 0.2.149.27 (1583)
URLs (if applicable) : any IPv6 url
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
     Safari 3: not tested
    Firefox 3: OK
         IE 7: OK

What steps will reproduce the problem?
1. Open any IPv6 url like : http://[2001:660:3001:4002::10] 
(www.renater.fr)
2.
3.

What is the expected result?

Showing IPv6 website

What happens instead?

Nothing, we areredirected to google as it does not support IPv6 addressing 
(I haven't checked if it even does a dns request for an IPv6 address when 
specifying text URL instead of IPv6 adddress).

Please provide any additional information below. Attach a screenshot if 
possible.
 
Comment 1 by niranjan@chromium.org, Sep 07, 2008
I don't think we have ever tested this over IPv6. CC'ing Darin who is currently
re-writing the HTTP stack used by Chromium.

This is also referenced by internal bug http://b/issue?id=1112222 Relevant comments
from that bug:

"To reproduce, enter http://[2001:4860:0:1001::68]/ into the URL bar. Chrome does a
Google search instead of going to the web site with IPv6 address 2001:4860:0:1001::68.

This is correct URL syntax as per RFC 2732 - http://tools.ietf.org/html/rfc2732"
Summary: IPv6 support needed
Status: Untriaged
Cc: da...@chromium.org
Labels: -Type-Bug -Area-Unknown Type-Feature Area-BrowserBackend
Comment 2 by wtc@chromium.org, Sep 08, 2008
I believe IPv6 address literal support is the responsibility of the GURL
library.  GURL needs to be able to parse the square brackets notation in
a URL such as http://[2001:660:3001:4002::10]
Cc: w...@chromium.org bre...@chromium.org
Comment 3 by brettw@chromium.org, Sep 15, 2008
I checked in a change by Erik Kline to make basic IPv6 handling work. It is not full 
canonicalization, but should be sufficient to get sites to load as far as our code is 
concerned (not that I know how to test it). There may be network layers that don't 
know about it yet.

Fixed in r2256
Status: Fixed
Comment 6 by johan.denoyer, Nov 08, 2008
Confirmed to be working in r5068.

Thanks a lot!!!
Comment 7 by mal.chromium, Dec 18, 2009
(No comment was entered for this change.)
Labels: -Area-BrowserBackend Area-Internals
Sign in to add a comment

Powered by Google Project Hosting