curl/tests/data/test2036

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

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

#
# Verify data after the test has been "shot"
<verify>
<errorcode>
23
</errorcode>
</verify>
</testcase>
test2036: verify -O with no slash at all in the URL Similar to test 76 but that test's URL has a slash just no file name part. 2014-10-09 10:50:26 -04:00			`<testcase>`
			`<info>`
			`<keywords>`
			`FAILURE`
			`</keywords>`
			`</info>`
			`#`
			`# Server-side`
			`<reply>`
			`</reply>`

			`#`
			`# Client-side`
			`<client>`
			`<server>`
			`none`
			`</server>`
			`<features>`
			`http`
			`</features>`
			`<name>`
			`HTTP, -O with no slash at all in the URL`
			`</name>`
			`<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			`%HOSTIP:%NOLISTENPORT -O`
test2036: verify -O with no slash at all in the URL Similar to test 76 but that test's URL has a slash just no file name part. 2014-10-09 10:50:26 -04:00			`</command>`
			`</client>`

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