Updates:
Cc: [email protected]
Comment #4 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
Ok... Well, looking at Mark's change it seems it _should_ be addressing
this case too.
In particular ShouldTryNextAddress() looks to be checking for failure to
connect errors, so perhaps we are
getting an error code it doesn't expect?
Can you try running on a ToT build with --enable-logging --log-level=0 and
look for any "connect failed:
XXX" INFO logs?
http://src.chromium.org/viewvc/chrome/trunk/src/net/socket/tcp_client_socket_libevent.cc?
r1=26051&r2=26050
--
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
-~----------~----~----~----~------~----~------~--~---
