curl/tests/data/test302

<testcase>
#
# Server-side
<reply>
MOOOOO
</reply>

#
# Client-side
<client>
<features>
SSL
</features>
<server>
https
</server>
 <name>
HTTPS GET over HTTP proxy fails
 </name>
 <command>
-k -U fake:user -x %HOSTIP:%HTTPPORT https://bad.fakeurl-to.test/slash/302
</command>
</client>

#
# Verify data after the test has been "shot"
<verify>
<errorcode>
56
</errorcode>
<strip>
^User-Agent:.*
</strip>
<protocol>
</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>`
HTTPS test case 2001-09-18 11:13:40 -04:00			`#`
			`# Server-side`
			`<reply>`
test case 503 entered the dir 2002-12-13 11:17:27 -05:00			`MOOOOO`
HTTPS test case 2001-09-18 11:13:40 -04:00			`</reply>`

			`#`
			`# Client-side`
			`<client>`
properly mark tests as requiring feature 'SSL' 2005-01-30 07:53:05 -05:00			`<features>`
			`SSL`
			`</features>`
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>`
			`https`
			`</server>`
HTTPS test case 2001-09-18 11:13:40 -04:00			`<name>`
			`HTTPS GET over HTTP proxy fails`
			`</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			`-k -U fake:user -x %HOSTIP:%HTTPPORT https://bad.fakeurl-to.test/slash/302`
HTTPS test case 2001-09-18 11:13:40 -04:00			`</command>`
A minor "syntax error" in numerous test files corrected 2005-01-25 16:45:03 -05:00			`</client>`
HTTPS test case 2001-09-18 11:13:40 -04:00
			`#`
			`# Verify data after the test has been "shot"`
			`<verify>`
			`<errorcode>`
updated error code 2002-04-10 10:05:52 -04:00			`56`
HTTPS test case 2001-09-18 11:13:40 -04:00			`</errorcode>`
			`<strip>`
			`^User-Agent:.*`
			`</strip>`
			`<protocol>`
			`</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>`