1
0
mirror of https://github.com/moparisthebest/curl synced 2024-11-17 06:55:02 -05:00
curl/tests/data/test281
Daniel Stenberg da58d03ff7 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.
2006-11-25 13:32:04 +00:00

64 lines
902 B
Plaintext

<info>
<keywords>
HTTP
HTTP PUT
</keywords>
</info>
# Server-side
<reply>
<data>
HTTP/1.1 100 Continue
HTTP/1.1 401 Bad Auth swsclose
Date: Thu, 09 Nov 2010 14:49:00 GMT
WWW-Authenticate: Basic Realm=authenticate
Server: test-server/fake
</data>
<datacheck>
HTTP/1.1 100 Continue
</datacheck>
</reply>
# Client-side
<client>
<server>
http
</server>
<name>
HTTP PUT from file with 100 + 401 responses and -f without auth given
</name>
<command>
http://%HOSTIP:%HTTPPORT/we/want/281 -f -T log/test281.txt
</command>
<file name="log/test281.txt">
Weird
file
to
upload
</file>
</client>
# Verify data after the test has been "shot"
<verify>
<errorcode>
22
</errorcode>
<strip>
^User-Agent:.*
</strip>
<protocol>
PUT /we/want/281 HTTP/1.1
Host: %HOSTIP:%HTTPPORT
Accept: */*
Content-Length: 38
Expect: 100-continue
Weird
file
to
upload
</protocol>
</verify>