curl/tests/data/test1427

<testcase>
<info>
<keywords>
integer overflow
</keywords>
</info>

#
# Client-side
<client>
<server>
none
</server>
 <name>
too large -m timeout value
 </name>
 <command>
http://%HOSTIP:%NOLISTENPORT/1427 -m 184467440737095510
</command>
</client>

#
# Verify data after the test has been "shot"
<verify>
<errorcode>
2
</errorcode>
</verify>
</testcase>
test1427: verify command line parser integer overflow detection 2017-08-07 03:33:25 +08:00			`<testcase>`
			`<info>`
			`<keywords>`
			`integer overflow`
			`</keywords>`
			`</info>`

			`#`
			`# Client-side`
			`<client>`
			`<server>`
			`none`
			`</server>`
			`<name>`
			`too large -m timeout value`
			`</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 22:00:31 +08:00			`http://%HOSTIP:%NOLISTENPORT/1427 -m 184467440737095510`
test1427: verify command line parser integer overflow detection 2017-08-07 03:33:25 +08:00			`</command>`
			`</client>`

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