diff options
| author | agl@chromium.org <agl@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-10-05 21:04:13 +0000 |
|---|---|---|
| committer | agl@chromium.org <agl@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-10-05 21:04:13 +0000 |
| commit | da5b6de33c18e49a8c1f3fb3c05f779e07a2240d (patch) | |
| tree | 4525e52a3213d2441cf70f0063303724fd47b25f /gfx/path.cc | |
| parent | ccfa0e5964dde0f5697a9d62e6e0f58951ad8871 (diff) | |
| download | chromium_src-da5b6de33c18e49a8c1f3fb3c05f779e07a2240d.zip chromium_src-da5b6de33c18e49a8c1f3fb3c05f779e07a2240d.tar.gz chromium_src-da5b6de33c18e49a8c1f3fb3c05f779e07a2240d.tar.bz2 | |
Revert "net: uncork NSS sockets after a 200ms timeout."
Heap check went red. I don't think it was this patch, but reverting just to be
safe.
commit 502e93deaa8bb18030f9164b23480a79123d79e5
Author: agl@chromium.org <agl@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Date: Tue Oct 5 19:30:18 2010 +0000
net: uncork NSS sockets after a 200ms timeout.
We found that, after the recent corking change (r58838), we could end
up not sending the Finished message for an extended period of time.
This would cause servers to time out our SSL connections because they
thought that we were still performing the handshake.
With this change, we'll uncork and flush buffers after 200ms if no
application data is ready.
BUG=58017
TEST=Make HTTPS connections to Google sites. Check that the servers are terminating our idle connections.
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@61546 0039d316-1c4b-4281-b951-d872f2087c98
BUG=58017
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@61560 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'gfx/path.cc')
0 files changed, 0 insertions, 0 deletions