12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091929394 |
- <testcase>
- <info>
- <keywords>
- HTTP
- HTTP GET
- Resume
- FAILURE
- </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 beyond end of entirely-downloaded file, no server resume
- </name>
- <command>
- http://%HOSTIP:%HTTPPORT/1042 -C 200
- </command>
- <file name="log/curl1042.out">
- 012345678
- 012345678
- 012345678
- 012345678
- 012345678
- 012345678
- 012345678
- 012345678
- 012345678
- 012345678
- </file>
- </client>
- # Verify data after the test has been "shot"
- <verify>
- <errorcode>
- 33
- </errorcode>
- <strip>
- ^User-Agent:.*
- </strip>
- <protocol>
- GET /1042 HTTP/1.1
- Range: bytes=200-
- Host: %HOSTIP:%HTTPPORT
- Accept: */*
- </protocol>
- </verify>
- </testcase>
|