1<testcase> 2<info> 3<keywords> 4HTTP 5HTTP GET 6Resume 7</keywords> 8</info> 9 10# Server-side 11<reply> 12# Some servers (e.g. Apache 1.2) respond this way to an invalid byte range 13<data> 14HTTP/1.1 200 OK 15Connection: close 16Content-Length: 100 17Content-Type: text/plain 18 19012345678 20012345678 21012345678 22012345678 23012345678 24012345678 25012345678 26012345678 27012345678 28012345678 29</data> 30 31# The file data that exists at the start of the test must be included in 32# the verification. 33<datacheck> 34012345678 35012345678 36012345678 37012345678 38012345678 39012345678 40012345678 41012345678 42012345678 43012345678 44HTTP/1.1 200 OK 45Connection: close 46Content-Length: 100 47Content-Type: text/plain 48 49</datacheck> 50</reply> 51 52# Client-side 53<client> 54<server> 55http 56</server> 57 <name> 58HTTP GET resume at exactly the existing file size is fine 59 </name> 60 <command> 61http://%HOSTIP:%HTTPPORT/1434 -C 100 62</command> 63<file name="log/curl1434.out"> 64012345678 65012345678 66012345678 67012345678 68012345678 69012345678 70012345678 71012345678 72012345678 73012345678 74</file> 75</client> 76 77# Verify data after the test has been "shot" 78<verify> 79<strip> 80^User-Agent:.* 81</strip> 82<protocol> 83GET /1434 HTTP/1.1 84Host: %HOSTIP:%HTTPPORT 85Range: bytes=100- 86Accept: */* 87 88</protocol> 89</verify> 90</testcase> 91