curl/tests/data/test12

<testcase>
<info>
<keywords>
HTTP
HTTP GET
Range
</keywords>
</info>
# Server-side
<reply>
<data>
HTTP/1.1 206 Partial Content
Date: Mon, 13 Nov 2000 13:41:09 GMT
Server: Apache/1.3.11 (Unix) PHP/3.0.14
Last-Modified: Tue, 13 Jun 2000 12:10:00 GMT
ETag: "21025-dc7-39462498"
Accept-Ranges: bytes
Content-Length: 101
Content-Range: bytes 100-200/3527
Connection: close
Content-Type: text/html

ink="#ffffff" vlink="#cccccc">
<table width=100% cellspacing=0 cellpadding=0 border=0>
 <tr> 0123456
</data>
</reply>

# Client-side
<client>
<server>
http
</server>
 <name>
HTTP range support
 </name>
 <command>
http://%HOSTIP:%HTTPPORT/want/12 -r 100-200
</command>
</client>

# Verify data after the test has been "shot"
<verify>
<strip>
^User-Agent:.*
</strip>
<protocol>
GET /want/12 HTTP/1.1
Range: bytes=100-200
Host: 127.0.0.1:%HTTPPORT
Accept: */*

</protocol>
</verify>
</testcase>
Convert (most of) the test data files into genuine XML. A handful still are not, due mainly to the lack of support for XML character entities (e.g. & => & ). This will make it easier to validate test files using tools like xmllint, as well as edit and view them using XML tools. 2007-01-23 05:25:56 +03:00			`<testcase>`
keywords added 2005-04-17 03:15:19 +04:00			`<info>`
			`<keywords>`
			`HTTP`
			`HTTP GET`
keyword update 2005-04-27 13:59:47 +04:00			`Range`
keywords added 2005-04-17 03:15:19 +04:00			`</keywords>`
			`</info>`
test case converted to the new file format 2001-05-28 16:30:21 +04:00			`# Server-side`
			`<reply>`
			`<data>`
			`HTTP/1.1 206 Partial Content`
			`Date: Mon, 13 Nov 2000 13:41:09 GMT`
			`Server: Apache/1.3.11 (Unix) PHP/3.0.14`
			`Last-Modified: Tue, 13 Jun 2000 12:10:00 GMT`
			`ETag: "21025-dc7-39462498"`
			`Accept-Ranges: bytes`
			`Content-Length: 101`
			`Content-Range: bytes 100-200/3527`
			`Connection: close`
			`Content-Type: text/html`

			`ink="#ffffff" vlink="#cccccc">`
			`<table width=100% cellspacing=0 cellpadding=0 border=0>`
			`<tr> 0123456`
			`</data>`
			`</reply>`

			`# Client-side`
			`<client>`
Each test case now specifies which server(s) it needs, without relying on the test number. 2003-05-01 00:25:39 +04:00			`<server>`
			`http`
			`</server>`
test case converted to the new file format 2001-05-28 16:30:21 +04:00			`<name>`
			`HTTP range support`
			`</name>`
			`<command>`
Now the test servers and test cases can run on a custom port number. There's no fixed port numbers in use anymore. Starting now, the default ports the servers use are 8990 - 8993. There's no option to modify these yet, but changing the $base option in the top of the runtests.pl script. 2004-09-08 12:08:38 +04:00			`http://%HOSTIP:%HTTPPORT/want/12 -r 100-200`
test case converted to the new file format 2001-05-28 16:30:21 +04:00			`</command>`
A minor "syntax error" in numerous test files corrected 2005-01-26 00:45:03 +03:00			`</client>`
test case converted to the new file format 2001-05-28 16:30:21 +04:00
			`# Verify data after the test has been "shot"`
			`<verify>`
			`<strip>`
			`^User-Agent:.*`
			`</strip>`
			`<protocol>`
			`GET /want/12 HTTP/1.1`
			`Range: bytes=100-200`
Now the test servers and test cases can run on a custom port number. There's no fixed port numbers in use anymore. Starting now, the default ports the servers use are 8990 - 8993. There's no option to modify these yet, but changing the $base option in the top of the runtests.pl script. 2004-09-08 12:08:38 +04:00			`Host: 127.0.0.1:%HTTPPORT`
Modified the default HTTP Accept: header to only be Accept: / 2004-02-09 15:46:41 +03:00			`Accept: /`
test case converted to the new file format 2001-05-28 16:30:21 +04:00
			`</protocol>`
			`</verify>`
Convert (most of) the test data files into genuine XML. A handful still are not, due mainly to the lack of support for XML character entities (e.g. & => & ). This will make it easier to validate test files using tools like xmllint, as well as edit and view them using XML tools. 2007-01-23 05:25:56 +03:00			`</testcase>`