New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 68667 link

Starred by 4 users

Issue metadata

Status: WontFix
Owner:
Closed: Feb 2011
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature

Restricted
  • Only users with Commit permission may comment.



Sign in to add a comment

Friendly IPv6 error messages

Reported by m...@praseodym.net, Jan 5 2011

Issue description

Chrome Version       : 9.0.597.42 beta

When visiting an IPv6-only website (e.g. ipv6.google.com) without IPv6 connectivity, instead of failing with a general error message ("Oops! Google Chrome could not find …"), it'd be nice to have a more specific error message mentioning e.g. that the site is IPv6-only. The same could be done when only IPv6 connectivity is available.

This feature is purely an enhancement, but might prove very useful in the future when more IPv6-only websites will become available.
 
Labels: -Area-Undefined Area-Internals Internals-Network
Status: Untriaged
Labels: Mstone-12
Status: Assigned

Comment 3 by mmenke@google.com, Feb 1 2011

At the moment, I believe we specify only IPv4 addresses on DNS lookups on computers that don't have IPv6 addresses.  I'm not sure if changing how we do things is worth the effort of giving better error feedback.
Labels: -Type-Bug -Pri-2 -Mstone-12 Type-Feature Pri-3 Mstone-X
I am not sure there is much we can do about this  right now.

Since there isn't a good way for us to know when IPv6 connectivity is the underlying cause for the network failures.

We could special-case the ipv6.google.com case as suggested. Basically if our heuristic has probed IPv6 support as non-existent (no interface with IPv6 address), but yet getaddrinfo() has returned only IPv6 address choices, we could give a more specific failure message.

For now that is a pretty uncommon situation, taking out of the milestone 12 bucket.
Is it event possible to resolve IPv6 addresses without IPv6 connectivity?  On my home PC, getaddrinfo with AF_UNSPEC fails to resolve ipv6.google.com with either my ISP's or Google's name servers.

If all the work can't be done locally...Seems like it'll be quite a while before this is even worth thinking about.

Comment 6 by m...@praseodym.net, Feb 2 2011

A DNS IPv4 query can simply pass on AAAA-records; your DNS server doesn't know whether you have IPv6 connectivity or not. It could be that some ISP DNS servers or client-side resolvers filter out AAAA-records though.

Comment 7 by wtc@chromium.org, Feb 2 2011

Status: WontFix
Marked the bug WontFix.

It is getaddrinfo(AI_ADDRCONFIG) that decides, based on whether
the computer has an outgoing IPv6 network interface configured,
whether it needs to request AAAA records from a DNS server.
When getaddrinfo() returns EAI_NONAME, an application cannot
tell whether the hostname (ipv6.google.com) has no AAAA records
or getaddrinfo() didn't request AAAA records.  An application
will need to do extra work to distinguish between the two
reasons.

I wonder if we can use an ambiguous error message to cover both
cases.  Instead of

  Oops! Google Chrome could not find ipv6.google.com

we can say

  Oops! Google Chrome could not find ipv6.google.com or
  ipv6.google.com is on a network the computer is not
  connected to
I think you should reconsider 'Won't Fix'

This is needed - and Chromium shouldn't be alone.

if there is only an AAAA record and no A record and the user does not have IPv6 connectivity then display an error message along the lines of ‘This site is only available over IPv6. Your computer does not have IPv6 connectivity. Contact your ISP and demand IPv6 connectivity today.’

Maybe even use some geo-location services to determine the users IP address and display their ISP name.

This will be a problem as soon as one of the search engines start placing IPv6 only sites in search results.  It will probably happen first in India or China - but it will be happening soon.  Possibly this year.
Project Member

Comment 9 by bugdroid1@chromium.org, Oct 12 2012

Labels: Restrict-AddIssueComment-Commit
This issue has been closed for some time. No one will pay attention to new comments.
If you are seeing this bug or have new data, please click New Issue to start a new bug.
Project Member

Comment 10 by bugdroid1@chromium.org, Mar 10 2013

Labels: -Area-Internals -Internals-Network Cr-Internals Cr-Internals-Network

Sign in to add a comment