blob: b2b5a3b1730e889ab1ba51a1469274165cfc454b (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
|
<testcase>
<info>
<keywords>
HTTP
HTTP GET
Range
DELAY
</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>
|
