curl/tests/data/test303

<testcase>
<info>
<keywords>
HTTPS
HTTP GET
timeout
</keywords>
</info>

# Server-side
<reply>
<data>
HTTP/1.1 200 OK
Date: Thu, 09 Nov 2010 14:49:00 GMT
Connection: close

<html>result</html>
</data>
<postcmd>
wait 20
</postcmd>
</reply>

# Client-side
<client>
<features>
SSL
</features>
<server>
https
</server>
 <name>
HTTPS with 7 secs timeout
 </name>
 <command>
-k https://%HOSTIP:%HTTPSPORT/want/303 -m 7
</command>
</client>

# Verify data after the test has been "shot"
<verify>
<strip>
^User-Agent:.*
</strip>
<protocol>
GET /want/303 HTTP/1.1
Host: %HOSTIP:%HTTPSPORT
Accept: */*

</protocol>
<errorcode>
28
</errorcode>
</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>`
Fixed test to use HTTPS as documented. 2008-02-09 05:01:36 +03:00			`<info>`
			`<keywords>`
			`HTTPS`
			`HTTP GET`
			`timeout`
			`</keywords>`
			`</info>`

new tests 2001-11-03 02:09:02 +03:00			`# Server-side`
			`<reply>`
			`<data>`
			`HTTP/1.1 200 OK`
			`Date: Thu, 09 Nov 2010 14:49:00 GMT`
			`Connection: close`

			`<html>result</html>`
			`</data>`
			`<postcmd>`
Fixed test to use HTTPS as documented. 2008-02-09 05:01:36 +03:00			`wait 20`
new tests 2001-11-03 02:09:02 +03:00			`</postcmd>`
			`</reply>`

			`# Client-side`
			`<client>`
properly mark tests as requiring feature 'SSL' 2005-01-30 15:53:05 +03:00			`<features>`
			`SSL`
			`</features>`
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>`
			`https`
			`</server>`
new tests 2001-11-03 02:09:02 +03:00			`<name>`
Fixed test to use HTTPS as documented. 2008-02-09 05:01:36 +03:00			`HTTPS with 7 secs timeout`
new tests 2001-11-03 02:09:02 +03:00			`</name>`
			`<command>`
Fixed test to use HTTPS as documented. 2008-02-09 05:01:36 +03:00			`-k https://%HOSTIP:%HTTPSPORT/want/303 -m 7`
new tests 2001-11-03 02:09:02 +03:00			`</command>`
A minor "syntax error" in numerous test files corrected 2005-01-26 00:45:03 +03:00			`</client>`
new tests 2001-11-03 02:09:02 +03:00
			`# Verify data after the test has been "shot"`
			`<verify>`
			`<strip>`
			`^User-Agent:.*`
			`</strip>`
			`<protocol>`
			`GET /want/303 HTTP/1.1`
Fixed test to use HTTPS as documented. 2008-02-09 05:01:36 +03:00			`Host: %HOSTIP:%HTTPSPORT`
Modified the default HTTP Accept: header to only be Accept: / 2004-02-09 15:46:41 +03:00			`Accept: /`
new tests 2001-11-03 02:09:02 +03:00
			`</protocol>`
			`<errorcode>`
			`28`
			`</errorcode>`
			`</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>`