curl/tests/data/test2

<testcase>
<info>
<keywords>
HTTP
HTTP GET
HTTP Basic auth
</keywords>
</info>
#
# Server-side
<reply>
<data>
HTTP/1.1 200 OK
Date: Thu, 09 Nov 2010 14:49:00 GMT
Server: test-server/fake swsclose
Content-Type: text/html
Funny-head: yesyes

</data>
</reply>

#
# Client-side
<client>
<server>
http
</server>
 <name>
HTTP GET with user and password
 </name>
 <command>
 -u fake:user http://%HOSTIP:%HTTPPORT/2
</command>
</client>

#
# Verify data after the test has been "shot"
<verify>
<strip>
^User-Agent:.*
</strip>
<protocol>
GET /2 HTTP/1.1
Authorization: Basic ZmFrZTp1c2Vy
Host: 127.0.0.1:%HTTPPORT
Accept: */*

</protocol>
<data>
[insert full protocol verifiction dump here]
</data>
</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>`
started adding "keywords" for each test, to better allow us to sum up what kind of tests we have and how many tests that test certain features 2005-04-15 19:48:31 -04:00			`<info>`
			`<keywords>`
			`HTTP`
			`HTTP GET`
			`HTTP Basic auth`
			`</keywords>`
			`</info>`
new test case file format 2001-05-23 11:00:48 -04:00			`#`
			`# Server-side`
			`<reply>`
			`<data>`
			`HTTP/1.1 200 OK`
			`Date: Thu, 09 Nov 2010 14:49:00 GMT`
modified to work fine with the new persistant connection working test suite HTTP server 2003-07-19 19:57:08 -04:00			`Server: test-server/fake swsclose`
new test case file format 2001-05-23 11:00:48 -04:00			`Content-Type: text/html`
			`Funny-head: yesyes`

			`</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 case file format 2001-05-23 11:00:48 -04:00			`<name>`
			`HTTP GET with user and password`
			`</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 04:08:38 -04:00			`-u fake:user http://%HOSTIP:%HTTPPORT/2`
new test case file format 2001-05-23 11:00:48 -04:00			`</command>`
A minor "syntax error" in numerous test files corrected 2005-01-25 16:45:03 -05:00			`</client>`
new test case file format 2001-05-23 11:00:48 -04:00
			`#`
			`# Verify data after the test has been "shot"`
			`<verify>`
			`<strip>`
			`^User-Agent:.*`
			`</strip>`
			`<protocol>`
			`GET /2 HTTP/1.1`
			`Authorization: Basic ZmFrZTp1c2Vy`
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			`Host: 127.0.0.1:%HTTPPORT`
Modified the default HTTP Accept: header to only be Accept: / 2004-02-09 07:46:41 -05:00			`Accept: /`
new test case file format 2001-05-23 11:00:48 -04:00
			`</protocol>`
			`<data>`
			`[insert full protocol verifiction dump here]`
			`</data>`
			`</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>`