curl/tests/data/test504

# Server-side
<reply>
</reply>

# Client-side
<client>
<server>
none
</server>
# 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 127.0.0.1:55555
</command>
</client>

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

			`# Client-side`
			`<client>`
			`<server>`
no server needed 2003-03-16 01:12:46 +08:00			`none`
Added test case 504, using multi interface and a local proxy without anything listening on the port we use. 2002-12-16 23:30:10 +08:00			`</server>`
			`# tool is what to use instead of 'curl'`
			`<tool>`
			`lib504`
			`</tool>`

			`<name>`
			`simple multi through local proxy without listener`
			`</name>`
			`<command>`
Dan Fandrich's fix to use 127.0.0.1 instead of localhost to not depend on it resolving nicely 2004-09-23 02:21:45 +08:00			`http://%HOSTIP:%HTTPSPORT/504 127.0.0.1:55555`
Added test case 504, using multi interface and a local proxy without anything listening on the port we use. 2002-12-16 23:30:10 +08:00			`</command>`
			`</client>`

			`# Verify data after the test has been "shot"`
			`<verify>`
			`<errorcode>`
			`100`
			`</errorcode>`
			`</verify>`