summaryrefslogtreecommitdiffstats
path: root/chrome/common
diff options
context:
space:
mode:
authoragl@chromium.org <agl@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-11-08 21:03:30 +0000
committeragl@chromium.org <agl@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-11-08 21:03:30 +0000
commit0510362557c58a6d3f26b9681b06a0e605c9cfd5 (patch)
tree743e1d284e27d1a762ec8db53fa7720ad3d20a1b /chrome/common
parent08cf125f544b93da1ca4c3ed2840bce7fc9ff3fb (diff)
downloadchromium_src-0510362557c58a6d3f26b9681b06a0e605c9cfd5.zip
chromium_src-0510362557c58a6d3f26b9681b06a0e605c9cfd5.tar.gz
chromium_src-0510362557c58a6d3f26b9681b06a0e605c9cfd5.tar.bz2
net: update False Start blacklist processing for \r\n
It's not clear what's happening because I don't have a Windows machine and this was all done via try server runs: I think the problem is that the new False Start blacklist is larger than fread on Windows will read in one lump. That was causing the processing to fail on Windows. However, the simple fix of calling fread until its done didn't work because it never reads enough bytes. What's happening is that ftell is returning the true size of the file, but fread was converting \r\n to \n so the reported number of bytes read was too small. Why that wasn't happening before I'm not sure. I suspect that the file on disk on the Windows builders is \n and it's patch on the tryserver which is writing the file out with the extra \r bytes. Either way, this hopefully makes everything work. BUG=none TEST=net_unittests git-svn-id: svn://svn.chromium.org/chrome/trunk/src@65421 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/common')
0 files changed, 0 insertions, 0 deletions