Revert 110505 - Report ERR_CONTENT_LENGTH_MISMATCH when the count of bytes received doesn't match Content-Length.

This used to be reported as ERR_CONNECTION_CLOSED. Unfortunately, there are a number of misconfigured servers on the web which report a Content-Length completely divorced from reality. Other browsers display whatever data was received without reporting errors in this case, and Chrome now does the same.

An earlier CL simply removed error reporting for this case. However, some uses may want to still treat this like an error (such as URLFetcher), or could eventually treat the case as an error and recover (such as downloads).

Data received will be populated in the disk cache as a truncated entry, if the server advertises byte range support.

WebURLLoaderImpl ignores this for all async and sync resource loads. At some point it may want to selectively do this based on content type.

Downloads ignore the error, but no longer ignore ERR_CONNECTION_CLOSED.

Other uses will treat this like an error.

BUG=52847
TEST=Manually, go to a site that advertises a large content-length and closes the connection before writing so many bytes, and notice that the page now displays.

Automatic: HttpNetworkTransactionTest.LargeContentLengthThenClose, URLRequestTestHttp.GetZippedTest


Review URL: http://codereview.chromium.org/8496016

TBR=cbentzel@chromium.org

Review URL: http://codereview.chromium.org/8863002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@113562 0039d316-1c4b-4281-b951-d872f2087c98

2 files changed, 7 insertions, 33 deletions

diff --git a/net/http/http_network_transaction_unittest.cc b/net/http/http_network_transaction_unittest.cc
index dbd7e2f..d6f966c 100644
--- a/net/http/http_network_transaction_unittest.cc
+++ b/net/http/http_network_transaction_unittest.cc
@@ -6491,7 +6491,7 @@ TEST_F(HttpNetworkTransactionTest, LargeContentLengthThenClose) {
 
   std::string response_data;
   rv = ReadTransaction(trans.get(), &response_data);
-  EXPECT_EQ(ERR_CONTENT_LENGTH_MISMATCH, rv);
+  EXPECT_EQ(ERR_CONNECTION_CLOSED, rv);
 }
 
 TEST_F(HttpNetworkTransactionTest, UploadFileSmallerThanLength) {
diff --git a/net/http/http_stream_parser.cc b/net/http/http_stream_parser.cc
index 5ee1f22..cd3c9fa 100644
--- a/net/http/http_stream_parser.cc
+++ b/net/http/http_stream_parser.cc
@@ -530,38 +530,12 @@ int HttpStreamParser::DoReadBody() {
 }
 
 int HttpStreamParser::DoReadBodyComplete(int result) {
-  // When the connection is closed, there are numerous ways to interpret it.
-  //
-  //  - If a Content-Length header is present and the body contains exactly that
-  //    number of bytes at connection close, the response is successful.
-  //
-  //  - If a Content-Length header is present and the body contains fewer bytes
-  //    than promised by the header at connection close, it may indicate that
-  //    the connection was closed prematurely, or it may indicate that the
-  //    server sent an invalid Content-Length header. Unfortunately, the invalid
-  //    Content-Length header case does occur in practice and other browsers are
-  //    tolerant of it, so this is reported as an ERR_CONTENT_LENGTH_MISMATCH
-  //    rather than an ERR_CONNECTION_CLOSE.
-  //
-  //  - If chunked encoding is used and the terminating chunk has been processed
-  //    when the connection is closed, the response is successful.
-  //
-  //  - If chunked encoding is used and the terminating chunk has not been
-  //    processed when the connection is closed, it may indicate that the
-  //    connection was closed prematurely or it may indicate that the server
-  //    sent an invalid chunked encoding. We choose to treat it as
-  //    an invalid chunked encoding.
-  //
-  //  - If a Content-Length is not present and chunked encoding is not used,
-  //    connection close is the only way to signal that the response is
-  //    complete. Unfortunately, this also means that there is no way to detect
-  //    early close of a connection. No error is returned.
-  if (result == 0 && !IsResponseBodyComplete() && CanFindEndOfResponse()) {
-    if (chunked_decoder_.get())
-      result = ERR_INVALID_CHUNKED_ENCODING;
-    else
-      result = ERR_CONTENT_LENGTH_MISMATCH;
-  }
+  // If we didn't get a Content-Length and aren't using a chunked encoding,
+  // the only way to signal the end of a stream is to close the connection,
+  // so we don't treat that as an error, though in some cases we may not
+  // have completely received the resource.
+  if (result == 0 && !IsResponseBodyComplete() && CanFindEndOfResponse())
+    result = ERR_CONNECTION_CLOSED;
 
   // Filter incoming data if appropriate.  FilterBuf may return an error.
   if (result > 0 && chunked_decoder_.get()) {