diff options
| author | rch@chromium.org <rch@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-02-04 00:29:48 +0000 |
|---|---|---|
| committer | rch@chromium.org <rch@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-02-04 00:29:48 +0000 |
| commit | 0991485ae6cfb83c4a2ea82e4fce652e772d31a0 (patch) | |
| tree | bcdfac413c63564d86fa5e2516f5b026f8371237 /net/socket/socks_client_socket_unittest.cc | |
| parent | fcaad36622623077c948ec4557a8a028f16b21a2 (diff) | |
| download | chromium_src-0991485ae6cfb83c4a2ea82e4fce652e772d31a0.zip chromium_src-0991485ae6cfb83c4a2ea82e4fce652e772d31a0.tar.gz chromium_src-0991485ae6cfb83c4a2ea82e4fce652e772d31a0.tar.bz2 | |
Revert 118950 - 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.
Initially was http://codereview.chromium.org/8502024
which turned out to have problems with NTLM auth.
Review URL: http://codereview.chromium.org/9148011
TBR=rch@chromium.org
Review URL: https://chromiumcodereview.appspot.com/9310101
git-svn-id: svn://svn.chromium.org/chrome/branches/1025/src@120443 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'net/socket/socks_client_socket_unittest.cc')
0 files changed, 0 insertions, 0 deletions