Ignore Content-Length mismatches when Content-Length is too large.

net/http/http_network_transaction_spdy21_unittest.cc

Index: net/http/http_network_transaction_spdy21_unittest.cc
diff --git a/net/http/http_network_transaction_spdy21_unittest.cc b/net/http/http_network_transaction_spdy21_unittest.cc
index a777fa50959225676161e0d5a47e98ea13a5ec44..9cc683fa76ade163cdcdf4ed78988722f22ef986 100644
--- a/net/http/http_network_transaction_spdy21_unittest.cc
+++ b/net/http/http_network_transaction_spdy21_unittest.cc
@@ -6165,7 +6165,7 @@ TEST_F(HttpNetworkTransactionSpdy21Test, LargeContentLengthThenClose) {
 
   std::string response_data;
   rv = ReadTransaction(trans.get(), &response_data);
-  EXPECT_EQ(ERR_CONNECTION_CLOSED, rv);
+  EXPECT_EQ(OK, rv);

[rvargas (doing something else), 2012/03/24 01:06:50]

This is an interesting case. SPDY is really at a different layer, so it makes
sense that it should not care about any content-length mismatch... however,
there are some security implications with content-length mismatches in SSL
connections... and it sort of makes sense to be able to spec SPDY to enforce
something here.

In other words, seems OK to land this as is, but explore if we should do
something about it at least for SPDY (being a new implementation for everyone).

[cbentzel, 2012/03/24 01:24:35]

Yes, this is interesting. I am concerned about web compatibility issues with
SPDY proxies forwarding data along from incorrect HTTP backends - in that case
we may want this behavior to be permitted.

 }
 
 TEST_F(HttpNetworkTransactionSpdy21Test, UploadFileSmallerThanLength) {