curl/tests/data/test543

<testcase>
<info>
<keywords>
curl_easy_escape
</keywords>
</info>
# Server-side

# Client-side
<client>
<server>
none
</server>
<tool>
lib543
</tool>
 <name>
curl_easy_escape
 </name>
 <command>
-
</command>

</client>

# Verify data after the test has been "shot"
#
# There's no MTDM in the protocol here since this code doesn't ask for the
# time/date of the file
<verify>
<stdout>
%9C%26K%3DI%04%A1%01%E0%D8%7C%20%B7%EFS%29%FA%1DW%E1
</stdout>
</verify>
</testcase>
Alex Fishman reported a curl_easy_escape() problem that was made the function do wrong on all input bytes that are >= 0x80 (decimal 128) due to a signed / unsigned mistake in the code. I fixed it and added test case 543 to verify. 2007-09-30 18:40:24 -04:00			`<testcase>`
			`<info>`
			`<keywords>`
			`curl_easy_escape`
			`</keywords>`
			`</info>`
			`# Server-side`

			`# Client-side`
			`<client>`
			`<server>`
			`none`
			`</server>`
			`<tool>`
			`lib543`
			`</tool>`
			`<name>`
			`curl_easy_escape`
			`</name>`
			`<command>`
			`-`
			`</command>`

			`</client>`

			`# Verify data after the test has been "shot"`
			`#`
			`# There's no MTDM in the protocol here since this code doesn't ask for the`
			`# time/date of the file`
			`<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-01-31 18:58:58 -05:00			`<stdout>`
Alex Fishman reported a curl_easy_escape() problem that was made the function do wrong on all input bytes that are >= 0x80 (decimal 128) due to a signed / unsigned mistake in the code. I fixed it and added test case 543 to verify. 2007-09-30 18:40:24 -04:00			`%9C%26K%3DI%04%A1%01%E0%D8%7C%20%B7%EFS%29%FA%1DW%E1`
			`</stdout>`
			`</verify>`
			`</testcase>`