From da58d03ff7be9fc5e0219d95ce2f9932e2272473 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Sat, 25 Nov 2006 13:32:04 +0000 Subject: 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. --- tests/data/test239 | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'tests/data/test239') diff --git a/tests/data/test239 b/tests/data/test239 index 7a789b600..77e7ae296 100644 --- a/tests/data/test239 +++ b/tests/data/test239 @@ -16,7 +16,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. @@ -29,7 +29,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. -- cgit v1.2.3