curl/tests/data/test501

#
# Server-side
<reply name="1">
</reply>

# Client-side
<client>
<server>
file
</server>
# tool is what to use instead of 'curl'
<tool>
lib501
</tool>

 <name>
simple libcurl attempt operation without URL set
 </name>
 <command>
http://%HOSTIP:%HTTPPORT/501
</command>
</client>

#
# Verify data after the test has been "shot"
<verify>
<errorcode>
3
</errorcode>
</verify>
run tiny specific libcurl-testing tools 2002-12-12 07:12:01 -05:00			`#`
			`# Server-side`
			`<reply name="1">`
			`</reply>`

			`# Client-side`
			`<client>`
			`<server>`
corrected 2002-12-12 07:49:29 -05:00			`file`
run tiny specific libcurl-testing tools 2002-12-12 07:12:01 -05:00			`</server>`
			`# tool is what to use instead of 'curl'`
			`<tool>`
corrected 2002-12-12 07:49:29 -05:00			`lib501`
run tiny specific libcurl-testing tools 2002-12-12 07:12:01 -05:00			`</tool>`

			`<name>`
			`simple libcurl attempt operation without URL set`
			`</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			`http://%HOSTIP:%HTTPPORT/501`
run tiny specific libcurl-testing tools 2002-12-12 07:12:01 -05:00			`</command>`
			`</client>`

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