curl/tests/data/test33

<testcase>
<info>
<keywords>
HTTP
HTTP PUT
Resume
Content-Range
</keywords>
</info>
# Server-side
<reply>
<data>
HTTP/1.1 200 OK swsclose

</data>
</reply>

# Client-side
<client>
<server>
http
</server>
 <name>
HTTP PUT with resume
 </name>
<file name="log/test33.txt">
012345678
012345678
012345678
012345678
012345678
012345678
012345678
012345678
012345678
012345678
</file>
 <command>
http://%HOSTIP:%HTTPPORT/33 -Tlog/test33.txt -C 50
</command>
</client>

# Verify data after the test has been "shot"
<verify>
<protocol>
PUT /33 HTTP/1.1
Host: %HOSTIP:%HTTPPORT
Content-Range: bytes 50-99/100
User-Agent: curl/%VERSION
Accept: */*
Content-Length: 50
Expect: 100-continue

012345678
012345678
012345678
012345678
012345678
</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-22 21:25:56 -05:00			`<testcase>`
keywords added 2005-04-22 17:59:08 -04:00			`<info>`
			`<keywords>`
			`HTTP`
			`HTTP PUT`
Added some <keywords> sections and use some key words more consistently. 2007-10-11 21:44:22 -04:00			`Resume`
keywords added 2005-04-22 17:59:08 -04:00			`Content-Range`
			`</keywords>`
			`</info>`
New test cases added 2001-06-12 05:12:59 -04:00			`# Server-side`
			`<reply>`
			`<data>`
tests: Fix a couple of incomplete response lines 2014-07-08 06:47:58 -04:00			`HTTP/1.1 200 OK swsclose`
New test cases added 2001-06-12 05:12:59 -04:00
			`</data>`
			`</reply>`

			`# Client-side`
			`<client>`
Each test case now specifies which server(s) it needs, without relying on the test number. 2003-04-30 16:25:39 -04:00			`<server>`
			`http`
			`</server>`
New test cases added 2001-06-12 05:12:59 -04:00			`<name>`
			`HTTP PUT with resume`
			`</name>`
			`<file name="log/test33.txt">`
			`012345678`
			`012345678`
			`012345678`
			`012345678`
			`012345678`
			`012345678`
			`012345678`
			`012345678`
			`012345678`
			`012345678`
			`</file>`
			`<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 04:08:38 -04:00			`http://%HOSTIP:%HTTPPORT/33 -Tlog/test33.txt -C 50`
New test cases added 2001-06-12 05:12:59 -04:00			`</command>`
A minor "syntax error" in numerous test files corrected 2005-01-25 16:45:03 -05:00			`</client>`
New test cases added 2001-06-12 05:12:59 -04:00
			`# Verify data after the test has been "shot"`
			`<verify>`
			`<protocol>`
			`PUT /33 HTTP/1.1`
http: always send Host: header as first header ...after the method line: "Since the Host field-value is critical information for handling a request, a user agent SHOULD generate Host as the first header field following the request-line." / RFC 7230 section 5.4 Additionally, this will also make libcurl ignore multiple specified custom Host: headers and only use the first one. Test 1121 has been updated accordingly Bug: http://curl.haxx.se/bug/view.cgi?id=1491 Reported-by: Rainer Canavan 2015-03-11 19:50:46 -04:00			`Host: %HOSTIP:%HTTPPORT`
New test cases added 2001-06-12 05:12:59 -04:00			`Content-Range: bytes 50-99/100`
runtests: provide curl's version string as %VERSION for tests ... so that we can check HTTP requests for User-Agent: curl/%VERSION Update 600+ test cases accordingly. Closes #6037 2020-10-02 07:45:24 -04:00			`User-Agent: curl/%VERSION`
Modified the default HTTP Accept: header to only be Accept: / 2004-02-09 07:46:41 -05:00			`Accept: /`
New test cases added 2001-06-12 05:12:59 -04:00			`Content-Length: 50`
issue 12 fix 2004-03-05 07:54:18 -05:00			`Expect: 100-continue`
New test cases added 2001-06-12 05:12:59 -04:00
			`012345678`
			`012345678`
			`012345678`
			`012345678`
			`012345678`
			`</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-22 21:25:56 -05:00			`</testcase>`