curl/tests/data/test509

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

# Client-side
<client>
<server>
none
</server>
<features>
http
</features>
# tool is what to use instead of 'curl'
<tool>
lib509
</tool>

<name>
initialization with memory callbacks and actual usage
</name>
<command>
nothing
</command>
</client>

#
# Verify data after the test has been "shot"
<verify>
<stdout>
seen custom_calloc()
seen custom_malloc()
seen custom_realloc()
seen custom_free()
</stdout>
</verify>

</testcase>
test509: libcurl initialization with memory callbacks and actual usage 2013-03-13 21:49:50 +01:00			`<testcase>`
			`#`
			`# Server-side`
			`<reply>`
			`</reply>`

			`# Client-side`
			`<client>`
			`<server>`
			`none`
			`</server>`
tests: Added missing http feature to tests 509 & 1513 2014-01-24 23:14:00 +01:00			`<features>`
			`http`
			`</features>`
test509: libcurl initialization with memory callbacks and actual usage 2013-03-13 21:49:50 +01:00			`# tool is what to use instead of 'curl'`
			`<tool>`
			`lib509`
			`</tool>`

			`<name>`
			`initialization with memory callbacks and actual usage`
			`</name>`
			`<command>`
			`nothing`
			`</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			`<stdout>`
test509: libcurl initialization with memory callbacks and actual usage 2013-03-13 21:49:50 +01:00			`seen custom_calloc()`
			`seen custom_malloc()`
			`seen custom_realloc()`
			`seen custom_free()`
			`</stdout>`
			`</verify>`

			`</testcase>`