mirror of
https://github.com/moparisthebest/curl
synced 2024-08-13 17:03:50 -04:00
da58d03ff7
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.
75 lines
1.5 KiB
Plaintext
75 lines
1.5 KiB
Plaintext
<info>
|
|
<keywords>
|
|
HTTP
|
|
HTTP GET
|
|
followlocation
|
|
</keywords>
|
|
</info>
|
|
# Server-side
|
|
<reply>
|
|
<data>
|
|
HTTP/1.1 301 This is a weirdo text message swsclose
|
|
Date: Thu, 09 Nov 2010 14:49:00 GMT
|
|
Server: test-server/fake
|
|
Location: data/2760002.txt?coolsite=http://anotherurl/?a_second/2760002
|
|
Connection: close
|
|
|
|
This server reply is for testing a simple Location: following
|
|
|
|
</data>
|
|
<data2>
|
|
HTTP/1.1 200 Followed here fine swsclose
|
|
Date: Thu, 09 Nov 2010 14:49:00 GMT
|
|
Server: test-server/fake
|
|
Content-Length: 52
|
|
|
|
If this is received, the location following worked
|
|
|
|
</data2>
|
|
<datacheck>
|
|
HTTP/1.1 301 This is a weirdo text message swsclose
|
|
Date: Thu, 09 Nov 2010 14:49:00 GMT
|
|
Server: test-server/fake
|
|
Location: data/2760002.txt?coolsite=http://anotherurl/?a_second/2760002
|
|
Connection: close
|
|
|
|
HTTP/1.1 200 Followed here fine swsclose
|
|
Date: Thu, 09 Nov 2010 14:49:00 GMT
|
|
Server: test-server/fake
|
|
Content-Length: 52
|
|
|
|
If this is received, the location following worked
|
|
|
|
</datacheck>
|
|
</reply>
|
|
|
|
# Client-side
|
|
<client>
|
|
<server>
|
|
http
|
|
</server>
|
|
<name>
|
|
HTTP Location: following with multiple question marks in URLs
|
|
</name>
|
|
<command>
|
|
"http://%HOSTIP:%HTTPPORT/want?uri=http://anything/276?secondq/276" -L
|
|
</command>
|
|
</client>
|
|
|
|
# Verify data after the test has been "shot"
|
|
<verify>
|
|
<strip>
|
|
^User-Agent:.*
|
|
</strip>
|
|
<protocol>
|
|
GET /want?uri=http://anything/276?secondq/276 HTTP/1.1
|
|
Host: 127.0.0.1:%HTTPPORT
|
|
Accept: */*
|
|
|
|
GET /data/2760002.txt?coolsite=http://anotherurl/?a_second/2760002 HTTP/1.1
|
|
Host: 127.0.0.1:%HTTPPORT
|
|
Accept: */*
|
|
|
|
</protocol>
|
|
</verify>
|