aboutsummaryrefslogtreecommitdiff
path: root/tests/data/test91
diff options
context:
space:
mode:
authorDaniel Stenberg <daniel@haxx.se>2006-11-25 13:32:04 +0000
committerDaniel Stenberg <daniel@haxx.se>2006-11-25 13:32:04 +0000
commitda58d03ff7be9fc5e0219d95ce2f9932e2272473 (patch)
tree8d2c198822b1642ac20c3cc7b387cd24e1bb4970 /tests/data/test91
parent9ea3831c08fab5b320e381b1552964ff789316c7 (diff)
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.
Diffstat (limited to 'tests/data/test91')
-rw-r--r--tests/data/test912
1 files changed, 2 insertions, 0 deletions
diff --git a/tests/data/test91 b/tests/data/test91
index ad0545926..ae64b16ef 100644
--- a/tests/data/test91
+++ b/tests/data/test91
@@ -37,6 +37,7 @@ This is not the real page either!
HTTP/1.1 200 Things are fine in server land swsclose
Server: Microsoft-IIS/5.0
Content-Type: text/html; charset=iso-8859-1
+Content-Length: 32
Finally, this is the real page!
</data1002>
@@ -60,6 +61,7 @@ WWW-Authenticate: NTLM TlRMTVNTUAACAAAAAgACADAAAAAGgoEAc51AYVDgyNcAAAAAAAAAAG4Ab
HTTP/1.1 200 Things are fine in server land swsclose
Server: Microsoft-IIS/5.0
Content-Type: text/html; charset=iso-8859-1
+Content-Length: 32
Finally, this is the real page!
</datacheck>