curl/tests/data/test38

<testcase>
<info>
<keywords>
HTTP
HTTP GET
Resume
FAILURE
</keywords>
</info>
# Server-side
<reply>
<data nocheck="1">
HTTP/1.0 200 Mooo
Date: Mon, 13 Nov 2000 13:41:09 GMT
Server: myown/1.0
Connection: close

todelooooo lalalala yada yada, we know nothing about ranges ;-)
</data>
</reply>

# Client-side
<client>
<server>
http
</server>
 <name>
HTTP resume request without server supporting it
 </name>
 <command option="no-output">
http://%HOSTIP:%HTTPPORT/want/38 -C - --no-include -o log/fewl.txt
</command>
<file name="log/fewl.txt">
This text is here to simulate a partly downloaded file to resume
download on.
</file>
</client>

# Verify data after the test has been "shot"
<verify>
<errorcode>
33
</errorcode>
<strip>
^User-Agent:.*
</strip>
<protocol>
GET /want/38 HTTP/1.1
Range: bytes=78-
Host: %HOSTIP:%HTTPPORT
Accept: */*

</protocol>

# the download target file must remain untouched
<file name="log/fewl.txt">
This text is here to simulate a partly downloaded file to resume
download on.
</file>
</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 10:25:56 +08:00			`<testcase>`
keywords 2005-04-22 18:06:58 +08:00			`<info>`
			`<keywords>`
			`HTTP`
			`HTTP GET`
			`Resume`
test 256 is like test 38 but with proxy + proxy auth 2005-04-22 18:15:21 +08:00			`FAILURE`
keywords 2005-04-22 18:06:58 +08:00			`</keywords>`
			`</info>`
test case 38, try a HTTP download resume without the server supporting ranges 2002-01-08 17:31:40 +08:00			`# Server-side`
			`<reply>`
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 10:25:56 +08:00			`<data nocheck="1">`
test case 38, try a HTTP download resume without the server supporting ranges 2002-01-08 17:31:40 +08:00			`HTTP/1.0 200 Mooo`
			`Date: Mon, 13 Nov 2000 13:41:09 GMT`
			`Server: myown/1.0`
			`Connection: close`

			`todelooooo lalalala yada yada, we know nothing about ranges ;-)`
			`</data>`
			`</reply>`

			`# Client-side`
			`<client>`
Each test case now specifies which server(s) it needs, without relying on the test number. 2003-05-01 04:25:39 +08:00			`<server>`
			`http`
			`</server>`
test case 38, try a HTTP download resume without the server supporting ranges 2002-01-08 17:31:40 +08:00			`<name>`
			`HTTP resume request without server supporting it`
			`</name>`
			`<command option="no-output">`
- curl the tool now deals with its command line options somewhat differently! All boolean options (such as -O, -I, -v etc), both short and long versions, now always switch on/enable the option named. Using the same option multiple times thus make no difference. To switch off one of those options, you need to use the long version of the option and type --no-OPTION. Like to disable verbose mode you use --no-verbose! - Added --remote-name-all to curl, which if used changes the default for all given URLs to be dealt with as if -O is used. So if you want to disable that for a specific URL after --remote-name-all has been used, you muse use -o - or --no-remote-name. 2008-06-09 04:53:49 +08:00			`http://%HOSTIP:%HTTPPORT/want/38 -C - --no-include -o log/fewl.txt`
test case 38, try a HTTP download resume without the server supporting ranges 2002-01-08 17:31:40 +08:00			`</command>`
			`<file name="log/fewl.txt">`
			`This text is here to simulate a partly downloaded file to resume`
			`download on.`
			`</file>`
			`</client>`

			`# Verify data after the test has been "shot"`
			`<verify>`
			`<errorcode>`
			`33`
			`</errorcode>`
			`<strip>`
			`^User-Agent:.*`
			`</strip>`
			`<protocol>`
			`GET /want/38 HTTP/1.1`
			`Range: bytes=78-`
Replaced 127.0.0.1 with %HOSTIP where possible 2007-09-15 03:32:31 +08:00			`Host: %HOSTIP:%HTTPPORT`
Modified the default HTTP Accept: header to only be Accept: / 2004-02-09 20:46:41 +08:00			`Accept: /`
test case 38, try a HTTP download resume without the server supporting ranges 2002-01-08 17:31:40 +08:00
			`</protocol>`

			`# the download target file must remain untouched`
			`<file name="log/fewl.txt">`
			`This text is here to simulate a partly downloaded file to resume`
			`download on.`
			`</file>`
			`</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 10:25:56 +08:00			`</testcase>`