Venkat Akella found out that libcurl did not like HTTP responses that simply

responded with a single status line and no headers nor body. Starting now, a
HTTP response on a persistent connection (i.e not set to be closed after the
response has been taken care of) must have Content-Length or chunked
encoding set, or libcurl will simply assume that there is no body.

To my horror I learned that we had no less than 57(!) test cases that did bad
HTTP responses like this, and even the test http server (sws) responded badly
when queried by the test system if it is the test system. So although the
actual fix for the problem was tiny, going through all the newly failing test
cases got really painful and boring.

1 files changed, 2 insertions, 2 deletions

diff --git a/tests/data/test243 b/tests/data/test243
index f8ef686e7..614dfc0fe 100644
--- a/tests/data/test243
+++ b/tests/data/test243
@@ -36,7 +36,7 @@ Hey you, authenticate or go away!
 HTTP/1.1 200 Things are fine in proxy land swsclose

 Server: Microsoft-IIS/5.0

 Content-Type: text/html; charset=iso-8859-1

-Content-Length; 42

+Content-Length: 42

 

 Contents of that page you requested, sir.
 </data1002>
@@ -57,7 +57,7 @@ Content-Length: 34
 HTTP/1.1 200 Things are fine in proxy land swsclose

 Server: Microsoft-IIS/5.0

 Content-Type: text/html; charset=iso-8859-1

-Content-Length; 42

+Content-Length: 42

 

 Contents of that page you requested, sir.
 </datacheck>