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.
56 lines
1.0 KiB
Plaintext
56 lines
1.0 KiB
Plaintext
<info>
|
|
<keywords>
|
|
HTTP
|
|
HTTP GET
|
|
HTTP replaced headers
|
|
</keywords>
|
|
</info>
|
|
# Server-side
|
|
<reply>
|
|
<data>
|
|
HTTP/1.0 200 OK swsclose
|
|
Date: Thu, 09 Nov 2010 14:49:00 GMT
|
|
Content-Type: text/html
|
|
|
|
boo
|
|
</data>
|
|
</reply>
|
|
|
|
# Client-side
|
|
<client>
|
|
<server>
|
|
http
|
|
</server>
|
|
<name>
|
|
HTTP, send cookies when using custom Host:
|
|
</name>
|
|
<command>
|
|
http://%HOSTIP:%HTTPPORT/we/want/62 -b log/jar62.txt -H "Host: www.host.foo.com"
|
|
</command>
|
|
<file name="log/jar62.txt">
|
|
# Netscape HTTP Cookie File
|
|
# http://curlm.haxx.se/rfc/cookie_spec.html
|
|
# This file was generated by libcurl! Edit at your own risk.
|
|
|
|
.foo.com TRUE /we/want/ FALSE 1170327387 test yes
|
|
.host.foo.com TRUE /we/want/ FALSE 1170327387 test2 yes
|
|
.fake.host.foo.com TRUE /we/want/ FALSE 1170327387 test4 yes
|
|
|
|
.foo.com TRUE /moo TRUE 0 test3 maybe
|
|
</file>
|
|
</client>
|
|
|
|
# Verify data after the test has been "shot"
|
|
<verify>
|
|
<strip>
|
|
^User-Agent:.*
|
|
</strip>
|
|
<protocol>
|
|
GET /we/want/62 HTTP/1.1
|
|
Accept: */*
|
|
Cookie: test2=yes; test=yes
|
|
Host: www.host.foo.com
|
|
|
|
</protocol>
|
|
</verify>
|