Updates:
        Cc: [email protected] [email protected]

Comment #11 on issue 5480 by [email protected]: Trying to sign in at  
bofa.com results in UNKNOWN_ERROR about 75% of the time.
http://code.google.com/p/chromium/issues/detail?id=5480

Thanks a lot for the error code 12030.

http://msdn.microsoft.com/en-us/library/aa383770(VS.85).aspx
documents ERROR_WINHTTP_CONNECTION_ERROR (12030) as follows:

   ERROR_WINHTTP_CONNECTION_ERROR
   12030
   The connection with the server has been reset or terminated,
   or an incompatible SSL protocol was encountered. For example,
   WinHTTP version 5.1 does not support SSL2 unless the client
   specifically enables it.

My search for ERROR_WINHTTP_CONNECTION_ERROR in MSDN
(http://social.msdn.microsoft.com/Search/en-US/?query=ERROR_WINHTTP_CONNECTION_ERROR&ac=8)
showed that the five WinHTTP IO functions can all return
ERROR_WINHTTP_CONNECTION_ERROR, so it's not clear when it is
safe for us to handle this error by resending the request.
We'll need to be able to reproduce this error before we can
figure out how to fix this.

If you're willing to test our Dev channel releases, which use
our own network stack, please follow the instructions
in http://dev.chromium.org/getting-involved/dev-channel to
download and run Google Chrome Channel Changer to switch
to the Dev channel.  You still need to switch to the Dev
channel even if you were on the Dev channel before, because
we just added a new Beta channel and moved the Dev channel
subscribers to the Beta channel.  Note that the Dev channel
is the least stable of the three release channels.

--
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to