diff options
| author | cbentzel@chromium.org <cbentzel@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-10-23 12:51:42 +0000 |
|---|---|---|
| committer | cbentzel@chromium.org <cbentzel@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-10-23 12:51:42 +0000 |
| commit | c8cb9612733811e0b6cf4a313d35043e8dde6fdc (patch) | |
| tree | 22db770bccbd48080cdcef196456f57fb7e213cf /base | |
| parent | 7ef03e00c0b4b0e6b1998a6a3d69fafb6d630f12 (diff) | |
| download | chromium_src-c8cb9612733811e0b6cf4a313d35043e8dde6fdc.zip chromium_src-c8cb9612733811e0b6cf4a313d35043e8dde6fdc.tar.gz chromium_src-c8cb9612733811e0b6cf4a313d35043e8dde6fdc.tar.bz2 | |
Revert 63643 - Add Reset to ClientSocket::UseHistory, and call on TCP disconnect.
There were a few repeating failures after I landed this CL. They looked unrelated, but I decided to revert since I didn't have a ton of time to continue investigating. Will hopefully reland soon.
The HttpProxyClientSocket reuses the same TcpClientSocket in the case that it is trying to establish a tunnel through
an authenticating proxy, but the proxy closed the TCP connection.
Also, fix SetOmniboxSpeculation on the TCPClientSocket implementations.
BUG=54062
TEST=Tried normal connections to make sure histograms were only emitted once, as well as https tunnels through an authenticating proxy to ensure that the use_history was correctly reset.
Review URL: http://codereview.chromium.org/3360007
TBR=cbentzel@chromium.org
Review URL: http://codereview.chromium.org/4006004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@63648 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'base')
0 files changed, 0 insertions, 0 deletions