curl/tests/data/test1410

<testcase>
<info>
<keywords>
cmdline
FAILURE
</keywords>
</info>


#
# Client-side
<client>
<server>
none
</server>
 <name>
Pass in negative number to --max-time
 </name>
 <command>
http://%HOSTIP:%NOLISTENPORT/1410 --max-time -4
</command>
</client>

#
# Verify data after the test has been "shot"
<verify>
<errorcode>
2
</errorcode>
</verify>
</testcase>
tests: verify the stricter numeric option parser Test 1409 and 1410 verifies the stricter numeric option parser introduced the other day in commit f2b6ebed7b. 2012-07-12 00:32:23 +02:00			`<testcase>`
			`<info>`
			`<keywords>`
			`cmdline`
tests: add 'FAILURE' keywords to tests 1409 and 1410 2012-11-20 13:50:57 +01:00			`FAILURE`
tests: verify the stricter numeric option parser Test 1409 and 1410 verifies the stricter numeric option parser introduced the other day in commit f2b6ebed7b. 2012-07-12 00:32:23 +02:00			`</keywords>`
			`</info>`


			`#`
			`# Client-side`
			`<client>`
			`<server>`
			`none`
			`</server>`
			`<name>`
			`Pass in negative number to --max-time`
			`</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 16:00:31 +02:00			`http://%HOSTIP:%NOLISTENPORT/1410 --max-time -4`
tests: verify the stricter numeric option parser Test 1409 and 1410 verifies the stricter numeric option parser introduced the other day in commit f2b6ebed7b. 2012-07-12 00:32:23 +02:00			`</command>`
			`</client>`

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