diff options
| author | ukai@chromium.org <ukai@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-01-19 10:30:53 +0000 |
|---|---|---|
| committer | ukai@chromium.org <ukai@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-01-19 10:30:53 +0000 |
| commit | 7bab769c20fc49cd1fbd55177b8ce26b471d7c22 (patch) | |
| tree | f6ad33c152214f338e6694e7d557a017a00b6fee /net/proxy/proxy_resolver_mac.h | |
| parent | d58e172826d246e93777ba10087f73b63f206724 (diff) | |
| download | chromium_src-7bab769c20fc49cd1fbd55177b8ce26b471d7c22.zip chromium_src-7bab769c20fc49cd1fbd55177b8ce26b471d7c22.tar.gz chromium_src-7bab769c20fc49cd1fbd55177b8ce26b471d7c22.tar.bz2 | |
Fix secure websocket (wss) on Mac.
When SSLClientSocket of Mac reports certificate error (e.g. ERR_CERT_AUTHORITY_INVALID), it hasn't finish the SSL handshake and doesn't report the socket is connected.
So, even if we tricks the result from SSLClientSocket::Connect by HandleCertificateError, it will be handled as ERR_CONNECTION_FAILED because socket_->IsConnected() is false.
So, when SSLClientSocket::Connect reported certificate error and socket_->IsConnectedAndIdle() is false, get the certificate and retry establishing connection again with the certificate in allowed bad certificates, so we could ignore the certificate verify error.
Without this fix, websocket live experiment on mac always fails for secure connection.
BUG=32569
TEST=try open wss: connection and got open events.
Review URL: http://codereview.chromium.org/543111
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@36519 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'net/proxy/proxy_resolver_mac.h')
0 files changed, 0 insertions, 0 deletions