curl/tests/data/test87

<testcase>
<info>
<keywords>
[] range
FAILURE
</keywords>
</info>
#
# Server-side
<reply>
</reply>
#
# Client-side
<client>
<server>
none
</server>
 <name>
urlglob with bad -o #[num] usage
 </name>
 <command option="no-output">
"http://%HOSTIP:%HTTPPORT/[870001-870003]" -o "log/dumpit#2.dump"
</command>
</client>

#
# Verify data after the test has been "shot"
<verify>
<errorcode>
2
</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-22 21:25:56 -05:00			`<testcase>`
keyword update 2005-04-27 05:59:47 -04:00			`<info>`
			`<keywords>`
			`[] range`
			`FAILURE`
			`</keywords>`
			`</info>`
test87 verifies the new and better check for bad -o #[num] stuff 2003-08-14 09:37:32 -04:00			`#`
			`# Server-side`
			`<reply>`
			`</reply>`
			`#`
			`# Client-side`
			`<client>`
			`<server>`
			`none`
			`</server>`
			`<name>`
			`urlglob with bad -o #[num] usage`
			`</name>`
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			`<command option="no-output">`
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/[870001-870003]" -o "log/dumpit#2.dump"`
test87 verifies the new and better check for bad -o #[num] stuff 2003-08-14 09:37:32 -04:00			`</command>`
			`</client>`

			`#`
			`# Verify data after the test has been "shot"`
			`<verify>`
			`<errorcode>`
			`2`
			`</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-22 21:25:56 -05:00			`</testcase>`