[chromium-bugs] Issue 3001 in chromium: Handle TLS-intolerant servers

Issue 3001: Handle TLS-intolerant servers http://code.google.com/p/chromium/issues/detail?id=3001 Comment #5 by [EMAIL PROTECTED]: Fixed by r3017. r3387 contains some related cleanup (replacing a bitmask of SSL versions by SSLConfig). Issue attribute updates: Status: Fixed -- You rec

[chromium-bugs] Issue 3001 in chromium: Handle TLS-intolerant servers

Issue 3001: Handle TLS-intolerant servers http://code.google.com/p/chromium/issues/detail?id=3001 Comment #3 by [EMAIL PROTECTED]: Note: In MapSecurityError, we should map SEC_E_ALGORITHM_MISMATCH (0x80090331) to a network error code that indicates the client and server don't support a common ver

[chromium-bugs] Issue 3001 in chromium: Handle TLS-intolerant servers

Issue 3001: Handle TLS-intolerant servers http://code.google.com/p/chromium/issues/detail?id=3001 Comment #2 by [EMAIL PROTECTED]: (No comment was entered for this change.) Issue attribute updates: Status: Started -- You received this message because you are listed in the owner or CC

[chromium-bugs] Issue 3001 in chromium: Handle TLS-intolerant servers

Issue 3001: Handle TLS-intolerant servers http://code.google.com/p/chromium/issues/detail?id=3001 New issue report by [EMAIL PROTECTED]: The new HTTP stack needs to handle TLS-intolerant servers gracefully by retrying with SSL 3.0. One such server is https://shirley2.davidson.edu/. Issue att