curl/tests/data/test23

<info>
<keywords>
unsupported protocol
FAILURE
</keywords>
</info>
# Server-side
<reply>
<data>
</data>
</reply>

# Client-side
<client>
<server>
http
</server>
 <name>
unsupported protocol:// URL
 </name>
 <command>
htfp://%HOSTIP:%HTTPPORT/none.htfml
</command>
</client>

# Verify data after the test has been "shot"
<verify>
<errorcode>
1
</errorcode>
</verify>
keywords added 2005-04-16 19:15:19 -04:00			`<info>`
			`<keywords>`
			`unsupported protocol`
			`FAILURE`
			`</keywords>`
			`</info>`
nine new test cases 2001-08-07 08:42:23 -04:00			`# Server-side`
			`<reply>`
			`<data>`
			`</data>`
			`</reply>`

			`# Client-side`
			`<client>`
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>`
			`http`
			`</server>`
nine new test cases 2001-08-07 08:42:23 -04:00			`<name>`
			`unsupported protocol:// URL`
			`</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			`htfp://%HOSTIP:%HTTPPORT/none.htfml`
nine new test cases 2001-08-07 08:42:23 -04:00			`</command>`
A minor "syntax error" in numerous test files corrected 2005-01-25 16:45:03 -05:00			`</client>`
nine new test cases 2001-08-07 08:42:23 -04:00
			`# Verify data after the test has been "shot"`
			`<verify>`
			`<errorcode>`
			`1`
			`</errorcode>`
			`</verify>`