curl/tests/data/test1508

<testcase>
<info>
<keywords>
HTTP
multi
</keywords>
</info>

# Client-side
<client>
<server>
none
</server>
<tool>
lib1508
</tool>
 <name>
Close a multi handle without using it
 </name>
 <command>
http://%HOSTIP:%HTTPPORT/path/1508
</command>
</client>

# Verify data after the test has been "shot"
<verify>
<file name="log/stdout1508">
We are done
</file>
</verify>
</testcase>
Fix NULL pointer reference when closing an unused multi handle. 2013-02-10 22:57:58 +01:00			`<testcase>`
			`<info>`
			`<keywords>`
			`HTTP`
			`multi`
			`</keywords>`
			`</info>`

			`# Client-side`
			`<client>`
			`<server>`
			`none`
			`</server>`
			`<tool>`
			`lib1508`
			`</tool>`
			`<name>`
			`Close a multi handle without using it`
			`</name>`
			`<command>`
			`http://%HOSTIP:%HTTPPORT/path/1508`
			`</command>`
			`</client>`

			`# Verify data after the test has been "shot"`
			`<verify>`
testsuite: use binary output mode for custom curl test tools Do not try to convert line-endings to CRLF on Windows by setting stdout to binary mode, just like the curl tool does if --ascii is not specified. This should prevent corrupted stdout line-ending output like CRCRLF. In order to make the previously naive text-aware tests work with binary mode on Windows, text-mode is disabled for them if it is not actually part of the test case and line-endings are corrected. 2014-02-01 00:58:58 +01:00			`<file name="log/stdout1508">`
Fix NULL pointer reference when closing an unused multi handle. 2013-02-10 22:57:58 +01:00			`We are done`
			`</file>`
			`</verify>`
			`</testcase>`