ee521a1c88
This is already how curl is documented to behave in Everything curl, but in actuality only short POSTs skip this. This should knock 30 seconds off a full run of the test suite since the 100-continue timeout will no longer be hit. Closes #10740
82 lines
1.4 KiB
Plaintext
82 lines
1.4 KiB
Plaintext
<testcase>
|
|
<info>
|
|
<keywords>
|
|
HTTP
|
|
HTTP PUT
|
|
Expect
|
|
</keywords>
|
|
</info>
|
|
# Server-side
|
|
<reply>
|
|
# 417 means the server didn't like the Expect header
|
|
<data>
|
|
HTTP/1.1 417 OK swsbounce
|
|
Date: Tue, 09 Nov 2010 14:49:00 GMT
|
|
Server: test-server/fake
|
|
Content-Length: 0
|
|
|
|
</data>
|
|
<data1>
|
|
HTTP/1.1 200 OK
|
|
Date: Tue, 09 Nov 2010 14:49:00 GMT
|
|
Server: test-server/fake
|
|
Content-Length: 10
|
|
|
|
blablabla
|
|
</data1>
|
|
<datacheck>
|
|
HTTP/1.1 417 OK swsbounce
|
|
Date: Tue, 09 Nov 2010 14:49:00 GMT
|
|
Server: test-server/fake
|
|
Content-Length: 0
|
|
|
|
HTTP/1.1 200 OK
|
|
Date: Tue, 09 Nov 2010 14:49:00 GMT
|
|
Server: test-server/fake
|
|
Content-Length: 10
|
|
|
|
blablabla
|
|
</datacheck>
|
|
<servercmd>
|
|
no-expect
|
|
</servercmd>
|
|
</reply>
|
|
|
|
# Client-side
|
|
<client>
|
|
<server>
|
|
http
|
|
</server>
|
|
<name>
|
|
HTTP PUT with Expect: 100-continue and 417 response
|
|
</name>
|
|
<command>
|
|
http://%HOSTIP:%HTTPPORT/we/want/%TESTNUMBER -T log/test%TESTNUMBER.txt
|
|
</command>
|
|
# 1053700 x 'x', large enough to invoke the 100-continue behaviour
|
|
<file name="log/test%TESTNUMBER.txt">
|
|
%repeat[1053700 x x]%
|
|
</file>
|
|
</client>
|
|
|
|
# Verify data after the test has been "shot"
|
|
<verify>
|
|
<protocol>
|
|
PUT /we/want/%TESTNUMBER HTTP/1.1
|
|
Host: %HOSTIP:%HTTPPORT
|
|
User-Agent: curl/%VERSION
|
|
Accept: */*
|
|
Content-Length: 1053701
|
|
Expect: 100-continue
|
|
|
|
PUT /we/want/%TESTNUMBER HTTP/1.1
|
|
Host: %HOSTIP:%HTTPPORT
|
|
User-Agent: curl/%VERSION
|
|
Accept: */*
|
|
Content-Length: 1053701
|
|
|
|
%repeat[1053700 x x]%
|
|
</protocol>
|
|
</verify>
|
|
</testcase>
|