ap/lib/libcurl/curl-7.54.1/tests/data/test1117

<testcase>
<info>
<keywords>
HTTP
HTTP GET
Range
</keywords>
</info>

# Server-side
<reply>
<data nocheck="yes">
HTTP/1.1 416 Requested Range Not Satisfiable
Date: Thu, 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: Thu, 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: 1
</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/1117 http://%HOSTIP:%HTTPPORT/wantmore/11170001
</command>
</client>

# Verify data after the test has been "shot"
<verify>
<stdout>
HTTP/1.1 416 Requested Range Not Satisfiable
Date: Thu, 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: Thu, 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>

<strip>
^User-Agent:.*
</strip>
<protocol>
GET /want/1117 HTTP/1.1
Host: %HOSTIP:%HTTPPORT
Range: bytes=10-22
Accept: */*

GET /wantmore/11170001 HTTP/1.1
Host: %HOSTIP:%HTTPPORT
Range: bytes=10-22
Accept: */*

</protocol>
</verify>
</testcase>