curl/tests/data/test1117
Fabian Keil 9e6ec8b6d5
tests 1117,1238,1523: adjust writedelay servercmds
... so the delays are the same now that the unit
is in milliseconds.
2022-05-11 11:14:18 +02:00

87 lines
1.6 KiB
Plaintext

<testcase>
<info>
<keywords>
HTTP
HTTP GET
Range
</keywords>
</info>
# Server-side
<reply>
<data nocheck="yes">
HTTP/1.1 416 Requested Range Not Satisfiable
Date: Tue, 09 Sep 2010 14:49:00 GMT
Accept-Ranges: bytes
Content-Length: 115
This is a long error message that is large enough that the test server is
guaranteed to split it into two packets.
</data>
<data1>
HTTP/1.1 206 Partial Content
Date: Tue, 09 Sep 2010 14:49:01 GMT
Accept-Ranges: bytes
Content-Range: bytes 10-18/155
Content-Length: 13
Content-Type: text/plain
partial body
</data1>
<servercmd>
writedelay: 1000
</servercmd>
</reply>
# Client-side
<client>
<server>
http
</server>
<name>
HTTP with invalid range then another URL
</name>
<command>
-r 10-22 http://%HOSTIP:%HTTPPORT/want/%TESTNUMBER http://%HOSTIP:%HTTPPORT/wantmore/%TESTNUMBER0001
</command>
</client>
# Verify data after the test has been "shot"
<verify>
<stdout>
HTTP/1.1 416 Requested Range Not Satisfiable
Date: Tue, 09 Sep 2010 14:49:00 GMT
Accept-Ranges: bytes
Content-Length: 115
This is a long error message that is large enough that the test server is
guaranteed to split it into two packets.
HTTP/1.1 206 Partial Content
Date: Tue, 09 Sep 2010 14:49:01 GMT
Accept-Ranges: bytes
Content-Range: bytes 10-18/155
Content-Length: 13
Content-Type: text/plain
partial body
</stdout>
<protocol>
GET /want/%TESTNUMBER HTTP/1.1
Host: %HOSTIP:%HTTPPORT
Range: bytes=10-22
User-Agent: curl/%VERSION
Accept: */*
GET /wantmore/%TESTNUMBER0001 HTTP/1.1
Host: %HOSTIP:%HTTPPORT
Range: bytes=10-22
User-Agent: curl/%VERSION
Accept: */*
</protocol>
</verify>
</testcase>