curl/tests/data/test502

<testcase>
<info>
<keywords>
FILE
</keywords>
</info>
#
# Server-side
<reply>
<data>
foo
   bar swsclose
bar
   foo
moo
</data>
</reply>

# Client-side
<client>
<server>
file
</server>
# tool is what to use instead of 'curl'
<tool>
lib%TESTNUMBER
</tool>

 <name>
simple multi file:// get
 </name>
 <command>
file://%PWD/log/test%TESTNUMBER.txt
</command>
<file name="log/test%TESTNUMBER.txt">
foo
   bar swsclose
bar
   foo
moo
</file>
</client>

# Verify data after the test has been "shot"
<verify>
</verify>
</testcase>
Convert (most of) the test data files into genuine XML. A handful still are not, due mainly to the lack of support for XML character entities (e.g. & => & ). This will make it easier to validate test files using tools like xmllint, as well as edit and view them using XML tools. 2007-01-22 21:25:56 -05:00			`<testcase>`
Added missing <keywords> 2008-11-11 16:58:41 -05:00			`<info>`
			`<keywords>`
			`FILE`
			`</keywords>`
			`</info>`
test 502, multi interface with file:// 2002-12-13 08:39:39 -05:00			`#`
			`# Server-side`
			`<reply>`
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			`<data>`
test 502, multi interface with file:// 2002-12-13 08:39:39 -05:00			`foo`
modified to work fine with the new persistant connection working test suite HTTP server 2003-07-19 19:57:08 -04:00			`bar swsclose`
test 502, multi interface with file:// 2002-12-13 08:39:39 -05:00			`bar`
			`foo`
			`moo`
			`</data>`
			`</reply>`

			`# Client-side`
			`<client>`
			`<server>`
			`file`
			`</server>`
			`# tool is what to use instead of 'curl'`
			`<tool>`
tests: use %TESTNUMBER instead of fixed number This makes the tests easier to copy and relocate to other test numbers without having to update content. Closes #6738 2021-03-12 11:38:26 -05:00			`lib%TESTNUMBER`
test 502, multi interface with file:// 2002-12-13 08:39:39 -05:00			`</tool>`

			`<name>`
			`simple multi file:// get`
			`</name>`
			`<command>`
tests: use %TESTNUMBER instead of fixed number This makes the tests easier to copy and relocate to other test numbers without having to update content. Closes #6738 2021-03-12 11:38:26 -05:00			`file://%PWD/log/test%TESTNUMBER.txt`
test 502, multi interface with file:// 2002-12-13 08:39:39 -05:00			`</command>`
tests: use %TESTNUMBER instead of fixed number This makes the tests easier to copy and relocate to other test numbers without having to update content. Closes #6738 2021-03-12 11:38:26 -05:00			`<file name="log/test%TESTNUMBER.txt">`
test 502, multi interface with file:// 2002-12-13 08:39:39 -05:00			`foo`
modified to work fine with the new persistant connection working test suite HTTP server 2003-07-19 19:57:08 -04:00			`bar swsclose`
test 502, multi interface with file:// 2002-12-13 08:39:39 -05:00			`bar`
			`foo`
			`moo`
			`</file>`
			`</client>`

			`# Verify data after the test has been "shot"`
			`<verify>`
			`</verify>`
Convert (most of) the test data files into genuine XML. A handful still are not, due mainly to the lack of support for XML character entities (e.g. & => & ). This will make it easier to validate test files using tools like xmllint, as well as edit and view them using XML tools. 2007-01-22 21:25:56 -05:00			`</testcase>`