mirror of
https://github.com/moparisthebest/curl
synced 2024-11-11 20:15:03 -05: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.
44 lines
919 B
Plaintext
44 lines
919 B
Plaintext
# Server-side
|
|
<reply>
|
|
<data>
|
|
HTTP/1.1 200 beng swsclose
|
|
Server: Microsoft-IIS/6.0
|
|
Authentication-Info: Passport1.4 tname=MSPAuth,tname=MSPProf,tname=MSPConsent,tname=MSPSecAuth
|
|
Content-Type: text/html; charset=iso-8859-1
|
|
Content-Length: 26
|
|
|
|
This is not the real page
|
|
</data>
|
|
</reply>
|
|
|
|
# Client-side
|
|
<client>
|
|
#
|
|
<server>
|
|
http
|
|
</server>
|
|
<name>
|
|
HTTP POST --anyauth to server not requiring any auth at all
|
|
</name>
|
|
<command>
|
|
http://%HOSTIP:%HTTPPORT/174 -u testuser:testpass --anyauth -d "junkelijunk"
|
|
</command>
|
|
</client>
|
|
|
|
# Verify data after the test has been "shot"
|
|
<verify>
|
|
<strip>
|
|
^User-Agent:.*
|
|
</strip>
|
|
<protocol nonewline=yes>
|
|
POST /174 HTTP/1.1
|
|
User-Agent: curl/7.12.1-CVS (i686-pc-linux-gnu) libcurl/7.12.1-CVS OpenSSL/0.9.6b ipv6 zlib/1.1.4 GSS libidn/0.4.6
|
|
Host: 127.0.0.1:%HTTPPORT
|
|
Accept: */*
|
|
Content-Length: 11
|
|
Content-Type: application/x-www-form-urlencoded
|
|
|
|
junkelijunk
|
|
</protocol>
|
|
</verify>
|