Comment #10 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
eroman: The only relevant message I get is this: [7283:267:227313914743758:INFO:/b/slave/chromium-rel-mac/build/src/chrome/browser/renderer_host/render_view_host.cc(1076)] Failed Provisional Load: http://www.sofaraway.org/ubuntu/tmp/chromium-popcon-8.png, error_code: -7 is_main_frame: 1 showing_repost_interstitial: 0 To add to the list of other browser behaviors in comment 5, Safari (on OS X) appears to wait about 80 seconds and then falls back to IPv4 like Firefox. wget prefers IPv4 by default, but when told to prefer IPv6 with --prefer-family=IPv6 it waits about 75 seconds before falling back to IPv4. I wonder what would happen for a host with two A records, rather than one A and one AAAA, where one of the A records was similarly broken? Would Chromium try the other (assuming it tried the bad one first)? Perhaps this functionality is broken, and that could easily be related to the mysterious errors mentioned in comment 1... -- 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 -~----------~----~----~----~------~----~------~--~---
