summaryrefslogtreecommitdiffstats
path: root/chrome_frame/chrome_launcher.cc
diff options
context:
space:
mode:
authoragl@chromium.org <agl@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2011-01-11 22:03:18 +0000
committeragl@chromium.org <agl@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2011-01-11 22:03:18 +0000
commit8c405136853ae0c4db3d8ad37df2b6e8af287cae (patch)
tree9907089633cad2905246194a3f566a17e64b11c0 /chrome_frame/chrome_launcher.cc
parent36843ab0abc7239d0fc2eaa6fea2a85d357f6dba (diff)
downloadchromium_src-8c405136853ae0c4db3d8ad37df2b6e8af287cae.zip
chromium_src-8c405136853ae0c4db3d8ad37df2b6e8af287cae.tar.gz
chromium_src-8c405136853ae0c4db3d8ad37df2b6e8af287cae.tar.bz2
net: Disable False Start and clear the SSL client auth cache for HTTPS proxies on failure.
When performing TLS client auth with an HTTPS proxy, disable TLS false start to better handle SSL handshake failures, such as the HTTPS proxy requiring a client certificate. In addition, when an HTTPS proxy fails, ensure that it is removed from the SSL client auth cache, so that if the failure was due to an invalid client certificate, the user can be prompted to select one again. Depends on: http://codereview.chromium.org/6017010 Patch by: Ryan Sleevi BUG=66424 TEST=HttpNetworkTransactionTest.Proxy_ClientAuthCertCache git-svn-id: svn://svn.chromium.org/chrome/trunk/src@71096 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome_frame/chrome_launcher.cc')
0 files changed, 0 insertions, 0 deletions