diff options
author | cbentzel@chromium.org <cbentzel@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-06-30 15:28:02 +0000 |
---|---|---|
committer | cbentzel@chromium.org <cbentzel@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-06-30 15:28:02 +0000 |
commit | ac54efc81249bf1b855e63e0fc77d3082c0b221b (patch) | |
tree | 5f180d41e2053104d274d9258282e75502971c20 /tools | |
parent | 40ce1e443686a02fd1237b1791c6e9a7023cf0a0 (diff) | |
download | chromium_src-ac54efc81249bf1b855e63e0fc77d3082c0b221b.zip chromium_src-ac54efc81249bf1b855e63e0fc77d3082c0b221b.tar.gz chromium_src-ac54efc81249bf1b855e63e0fc77d3082c0b221b.tar.bz2 |
Revert 89600 - Treat ERR_CONNECTION_CLOSED as a succesful download.
=========================
Note: This revert is only temporary, to collect statistics for how frequently this case is encountered in the wild. This will be re-reverted shortly.
=========================
Some servers will send a Content-Length which exceeds the number of bytes sent in the message body.
Although this violates the RFC spec, other major browsers permit it
and treat a download as complete in that case. Chrome did as well
prior to M12, and now some users are unable to access the item that
they downloaded.
BUG=85549
TEST=Go to server which advertises larger Content-Length than number of bytes sent, confirm that the download is no longer reported as interrupted.
Review URL: http://codereview.chromium.org/7203004
TBR=cbentzel@chromium.org
Review URL: http://codereview.chromium.org/7246025
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@91134 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions