curl/tests/data/test333

<testcase>
<info>
<keywords>
command-line
</keywords>
</info>

#
# Server-side
<reply>
</reply>

#
# Client-side
<client>
<server>
none
</server>
 <name>
Try a non-boolean command line option with --no-
 </name>
 <command>
--no-proxy "hey" http://%HOSTIP:%NOLISTENPORT/333
</command>
</client>

#
# Verify data after the test has been "shot"
<verify>
# detected the bad --no- prefix
<errorcode>
2
</errorcode>
</verify>
</testcase>
curl: report error for "--no-" on non-boolean options Reported-by: Olen Andoni Fixes #3906 Closes #3907 2019-05-20 04:51:53 -04:00			`<testcase>`
			`<info>`
			`<keywords>`
			`command-line`
			`</keywords>`
			`</info>`

			`#`
			`# Server-side`
			`<reply>`
			`</reply>`

			`#`
			`# Client-side`
			`<client>`
			`<server>`
			`none`
			`</server>`
			`<name>`
			`Try a non-boolean command line option with --no-`
			`</name>`
			`<command>`
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			`--no-proxy "hey" http://%HOSTIP:%NOLISTENPORT/333`
curl: report error for "--no-" on non-boolean options Reported-by: Olen Andoni Fixes #3906 Closes #3907 2019-05-20 04:51:53 -04:00			`</command>`
			`</client>`

			`#`
			`# Verify data after the test has been "shot"`
			`<verify>`
			`# detected the bad --no- prefix`
			`<errorcode>`
			`2`
			`</errorcode>`
			`</verify>`
			`</testcase>`