2014-10-30 09:54:59 -04:00
|
|
|
<testcase>
|
|
|
|
<info>
|
|
|
|
<keywords>
|
|
|
|
HTTP
|
|
|
|
HTTP GET
|
|
|
|
Resume
|
|
|
|
</keywords>
|
|
|
|
</info>
|
|
|
|
|
|
|
|
# Server-side
|
|
|
|
<reply>
|
|
|
|
# Some servers (e.g. Apache 1.2) respond this way to an invalid byte range
|
|
|
|
<data>
|
|
|
|
HTTP/1.1 200 OK
|
|
|
|
Connection: close
|
|
|
|
Content-Length: 100
|
|
|
|
Content-Type: text/plain
|
|
|
|
|
|
|
|
012345678
|
|
|
|
012345678
|
|
|
|
012345678
|
|
|
|
012345678
|
|
|
|
012345678
|
|
|
|
012345678
|
|
|
|
012345678
|
|
|
|
012345678
|
|
|
|
012345678
|
|
|
|
012345678
|
|
|
|
</data>
|
|
|
|
|
|
|
|
# The file data that exists at the start of the test must be included in
|
|
|
|
# the verification.
|
|
|
|
<datacheck>
|
|
|
|
012345678
|
|
|
|
012345678
|
|
|
|
012345678
|
|
|
|
012345678
|
|
|
|
012345678
|
|
|
|
012345678
|
|
|
|
012345678
|
|
|
|
012345678
|
|
|
|
012345678
|
|
|
|
012345678
|
|
|
|
HTTP/1.1 200 OK
|
|
|
|
Connection: close
|
|
|
|
Content-Length: 100
|
|
|
|
Content-Type: text/plain
|
|
|
|
|
|
|
|
</datacheck>
|
|
|
|
</reply>
|
|
|
|
|
|
|
|
# Client-side
|
|
|
|
<client>
|
|
|
|
<server>
|
|
|
|
http
|
|
|
|
</server>
|
|
|
|
<name>
|
|
|
|
HTTP GET resume at exactly the existing file size is fine
|
|
|
|
</name>
|
|
|
|
<command>
|
|
|
|
http://%HOSTIP:%HTTPPORT/1434 -C 100
|
|
|
|
</command>
|
|
|
|
<file name="log/curl1434.out">
|
|
|
|
012345678
|
|
|
|
012345678
|
|
|
|
012345678
|
|
|
|
012345678
|
|
|
|
012345678
|
|
|
|
012345678
|
|
|
|
012345678
|
|
|
|
012345678
|
|
|
|
012345678
|
|
|
|
012345678
|
|
|
|
</file>
|
|
|
|
</client>
|
|
|
|
|
|
|
|
# Verify data after the test has been "shot"
|
|
|
|
<verify>
|
|
|
|
<protocol>
|
|
|
|
GET /1434 HTTP/1.1
|
|
|
|
Host: %HOSTIP:%HTTPPORT
|
2015-03-11 19:50:46 -04:00
|
|
|
Range: bytes=100-
|
2020-10-02 07:45:24 -04:00
|
|
|
User-Agent: curl/%VERSION
|
2014-10-30 09:54:59 -04:00
|
|
|
Accept: */*
|
|
|
|
|
|
|
|
</protocol>
|
|
|
|
</verify>
|
|
|
|
</testcase>
|