| commit | 15a3c20866a1de64fa731b03b8662ad0e89436dd | [log] [tgz] |
|---|---|---|
| author | [email protected] <[email protected]@0039d316-1c4b-4281-b951-d872f2087c98> | Mon Nov 21 18:32:01 2011 |
| committer | [email protected] <[email protected]@0039d316-1c4b-4281-b951-d872f2087c98> | Mon Nov 21 18:32:01 2011 |
| tree | ca07527ce12072cd336e8c243c17a9bb4bd005b0 | |
| parent | 82a8b9cc6d3e491d79256e6ec0bc715e8b2171cc [diff] |
Allow chrome to handle 407 auth challenges to CONNECT requests through HTTPS Proxies. This also changes the mechanism used to restart HttpProxyClientSocket requests with auth. Previously the transport socket would be Disconnected, and then re-Connected (which was not implemented for SSLClientSockets). However, the approach was problematic in the face of, for example, ipv6. The new approach is to close the HttpProxyClientSocket, and request a new socket from the pool. Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=110529 Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=110879 Review URL: http://codereview.chromium.org/8502024 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@110965 0039d316-1c4b-4281-b951-d872f2087c98