Comment #8 on issue 23364 by l.colitti: 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
In a web browser, the user is probably not going to be interested in a page that loads minutes after he made the request. I think the proper thing to do here would be to have a shorter connect() timeout (say 5 or 10 seconds) and then try the next address, possibly removing the AAAA record from the DNS cache since it was known not to work. -- 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 -~----------~----~----~----~------~----~------~--~---
