curl/tests/data/test1269

<testcase>
<info>
<keywords>
--retry-delay
</keywords>
</info>

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

#
# Client-side
<client>
<server>
none
</server>
 <name>
too large --retry-delay value
 </name>
 <command>
--retry 3 --retry-delay 9223372036854776 http://%HOSTIP:%NOLISTENPORT/1269
</command>
</client>

#
# Verify data after the test has been "shot"
<verify>
<errorcode>
2
</errorcode>
</verify>
</testcase>
curl: cap the maximum allowed values for retry time arguments ... to avoid integer overflows later when multiplying with 1000 to convert seconds to milliseconds. Added test 1269 to verify. Reported-by: Jason Lee Closes #4166 2019-07-29 16:10:13 -04:00			`<testcase>`
			`<info>`
			`<keywords>`
			`--retry-delay`
			`</keywords>`
			`</info>`

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

			`#`
			`# Client-side`
			`<client>`
			`<server>`
			`none`
			`</server>`
			`<name>`
			`too large --retry-delay 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 10:00:31 -04:00			`--retry 3 --retry-delay 9223372036854776 http://%HOSTIP:%NOLISTENPORT/1269`
curl: cap the maximum allowed values for retry time arguments ... to avoid integer overflows later when multiplying with 1000 to convert seconds to milliseconds. Added test 1269 to verify. Reported-by: Jason Lee Closes #4166 2019-07-29 16:10:13 -04:00			`</command>`
			`</client>`

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