curl/tests/data/test504

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

# Client-side
<client>
<server>
none
</server>
<features>
http
</features>
# tool is what to use instead of 'curl'
<tool>
lib504
</tool>

 <name>
simple multi through local proxy without listener
 </name>
 <command>
http://%HOSTIP:%HTTPSPORT/504 %HOSTIP:55555
</command>
</client>

# Verify data after the test has been "shot"
<verify>
<errorcode>
100
</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>`
Added test case 504, using multi interface and a local proxy without anything listening on the port we use. 2002-12-16 18:30:10 +03:00			`# Server-side`
			`<reply>`
			`</reply>`

			`# Client-side`
			`<client>`
			`<server>`
no server needed 2003-03-15 20:12:46 +03:00			`none`
Added test case 504, using multi interface and a local proxy without anything listening on the port we use. 2002-12-16 18:30:10 +03:00			`</server>`
Updated the test harness to check for protocol support before running each test, fixing KNOWN_BUGS #11. Fixed some tests to more accurately specify their required servers and features. 2007-03-10 00:01:39 +03:00			`<features>`
			`http`
			`</features>`
Added test case 504, using multi interface and a local proxy without anything listening on the port we use. 2002-12-16 18:30:10 +03:00			`# tool is what to use instead of 'curl'`
			`<tool>`
			`lib504`
			`</tool>`

			`<name>`
			`simple multi through local proxy without listener`
			`</name>`
			`<command>`
Replaced 127.0.0.1 with %HOSTIP where possible 2007-09-14 23:32:31 +04:00			`http://%HOSTIP:%HTTPSPORT/504 %HOSTIP:55555`
Added test case 504, using multi interface and a local proxy without anything listening on the port we use. 2002-12-16 18:30:10 +03:00			`</command>`
			`</client>`

			`# Verify data after the test has been "shot"`
			`<verify>`
			`<errorcode>`
			`100`
			`</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>`