curl/tests/data/test514

<testcase>
<info>
<keywords>
HTTP
HTTP HEAD
</keywords>
</info>
#
# Server-side
<reply>
<data>
HTTP/1.1 200 OK
Date: Thu, 09 Nov 2010 14:49:00 GMT
Server: test-server/fake
Last-Modified: Tue, 13 Jun 2000 12:10:00 GMT
ETag: "21025-dc7-39462498"
Accept-Ranges: bytes
Content-Length: 6
Connection: close
Content-Type: text/html
Funny-head: yesyes

</data>
</reply>

#
# Client-side
<client>
<server>
http
</server>
<tool>
lib514
</tool>
 <name>
First set options to POST and then to make HEAD
 </name>
# the 1s post-command delay helps to prevent a spurious failure on s390
 <command delay="1">
http://%HOSTIP:%HTTPPORT/514
</command>
</client>

#
# Verify data after the test has been "shot"
<verify>
<protocol>
HEAD /514 HTTP/1.1
Host: %HOSTIP:%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-22 21:25:56 -05:00			`<testcase>`
tests: add keywords for a couple of HTTP tests 2012-11-19 11:54:52 -05:00			`<info>`
			`<keywords>`
			`HTTP`
			`HTTP HEAD`
			`</keywords>`
			`</info>`
NOBODY set TRUE after a POST makes a good HEAD now 2004-06-30 07:09:16 -04:00			`#`
			`# Server-side`
			`<reply>`
testsuite: use binary output mode for custom curl test tools Do not try to convert line-endings to CRLF on Windows by setting stdout to binary mode, just like the curl tool does if --ascii is not specified. This should prevent corrupted stdout line-ending output like CRCRLF. In order to make the previously naive text-aware tests work with binary mode on Windows, text-mode is disabled for them if it is not actually part of the test case and line-endings are corrected. 2014-01-31 18:58:58 -05:00			`<data>`
			`HTTP/1.1 200 OK`
			`Date: Thu, 09 Nov 2010 14:49:00 GMT`
			`Server: test-server/fake`
			`Last-Modified: Tue, 13 Jun 2000 12:10:00 GMT`
			`ETag: "21025-dc7-39462498"`
			`Accept-Ranges: bytes`
			`Content-Length: 6`
			`Connection: close`
			`Content-Type: text/html`
			`Funny-head: yesyes`

NOBODY set TRUE after a POST makes a good HEAD now 2004-06-30 07:09:16 -04:00			`</data>`
			`</reply>`

			`#`
			`# Client-side`
			`<client>`
			`<server>`
			`http`
			`</server>`
			`<tool>`
			`lib514`
			`</tool>`
			`<name>`
			`First set options to POST and then to make HEAD`
			`</name>`
add 1s post-command delay to tests 513 and 514 addressing http://curl.haxx.se/mail/lib-2009-12/0031.html 2010-04-27 02:47:30 -04:00			`# the 1s post-command delay helps to prevent a spurious failure on s390`
			`<command delay="1">`
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/514`
NOBODY set TRUE after a POST makes a good HEAD now 2004-06-30 07:09:16 -04:00			`</command>`
			`</client>`

			`#`
			`# Verify data after the test has been "shot"`
			`<verify>`
			`<protocol>`
			`HEAD /514 HTTP/1.1`
Replaced 127.0.0.1 with %HOSTIP where possible 2007-09-14 15:32:31 -04:00			`Host: %HOSTIP:%HTTPPORT`
NOBODY set TRUE after a POST makes a good HEAD now 2004-06-30 07:09:16 -04:00			`Accept: /`

			`</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>`