Comment #5 on issue 23364 by [email protected]: Chrome does not fall back to IPv4 when using IPv6 fails with Webpage Not Available http://code.google.com/p/chromium/issues/detail?id=23364
I believe this is not the same problem as 12711. The problem is, the domain has a AAAA record, and my machine has IPv6, but the specified AAAA record just leads to a black hole. Since IPv6 is the preferred protocol, it just keeps trying forever to connect. Here's how different browsers react to this condition on my machine: Firefox: hangs for a few minutes (yes, minutes), then loads the page, presumably via its IPv4 address. curl: same behavior as Firefox Chrome: Waits a few minutes, then reports "Error 7 (net::ERR_TIMED_OUT): The operation timed out." It's hard to say what the correct behavior is though. In this case, it's the server operator's fault for pointing to a dead address, but this can also turn up if the user is on a network which provides an apparently-valid IPv6 address, but blackholes all the packets. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
