curl/tests/data/test76

<testcase>
<info>
<keywords>
FAILURE
</keywords>
</info>
#
# Server-side
<reply>
</reply>

#
# Client-side
<client>
<server>
none
</server>
<features>
http
</features>
 <name>
HTTP, -O with no file name part in the URL
 </name>
 <command option="no-output">
http://%HOSTIP:%NOLISTENPORT/76/ -O
</command>
</client>

#
# Verify data after the test has been "shot"
<verify>
<errorcode>
23
</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>`
keywords added 2005-04-22 17:59:08 -04:00			`<info>`
			`<keywords>`
			`FAILURE`
			`</keywords>`
			`</info>`
more tests 2003-08-06 19:45:59 -04:00			`#`
			`# Server-side`
			`<reply>`
			`</reply>`

			`#`
			`# Client-side`
			`<client>`
			`<server>`
			`none`
			`</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-09 16:01:39 -05:00			`<features>`
			`http`
			`</features>`
more tests 2003-08-06 19:45:59 -04:00			`<name>`
			`HTTP, -O with no file name part in the URL`
			`</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">`
tests: Stop referring to server ports when they're not used Several tests referred to specific server ports even when the test didn't actually use that server or specify that it's needed. In such cases, the test harness substitutes the text "[not running]" as the port number which causes many such tests to fail due to the inability to parse the URL. These tests are changed to use %NOLISTENPORT which will always be substituted correctly. 2020-04-30 10:00:31 -04:00			`http://%HOSTIP:%NOLISTENPORT/76/ -O`
more tests 2003-08-06 19:45:59 -04:00			`</command>`
			`</client>`

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