Comment #15 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 wonder why we've established our own higher-level timeout around this. The timeout was added by http://codereview.chromium.org/160499 to improve performance of the socket-late- binding feature (which according to histograms had a tail of dangling requests that were taking forever). Seeing how late-binding isn't enabled by default anyways, it should be safe to crank this up. For a deeper fix (maybe get rid of the timeout alltogether) I will talk it through with Will when he gets back. -- 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 -~----------~----~----~----~------~----~------~--~---
