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/%LOGDIR/test%TESTNUMBER.txt
</command>
<file name="%LOGDIR/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-23 10:25:56 +08:00			`<testcase>`
Added missing <keywords> 2008-11-12 05:58:41 +08:00			`<info>`
			`<keywords>`
			`FILE`
			`</keywords>`
			`</info>`
test 502, multi interface with file:// 2002-12-13 21:39:39 +08: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-02-01 07:58:58 +08:00			`<data>`
test 502, multi interface with file:// 2002-12-13 21:39:39 +08:00			`foo`
modified to work fine with the new persistant connection working test suite HTTP server 2003-07-20 07:57:08 +08:00			`bar swsclose`
test 502, multi interface with file:// 2002-12-13 21:39:39 +08: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-13 00:38:26 +08:00			`lib%TESTNUMBER`
test 502, multi interface with file:// 2002-12-13 21:39:39 +08:00			`</tool>`

tests: remove leading spaces from some tags The threee tags `<name>`, `</name>` and `<command>` were frequently used with a leading space that this removes. The reason this habbit is so widespread in testcases is probably that they have been copy and pasted. Hence, fixing them all now might curb this practice from now on. Closes #12028 2023-10-04 17:35:54 +08:00			`<name>`
test 502, multi interface with file:// 2002-12-13 21:39:39 +08:00			`simple multi file:// get`
tests: remove leading spaces from some tags The threee tags `<name>`, `</name>` and `<command>` were frequently used with a leading space that this removes. The reason this habbit is so widespread in testcases is probably that they have been copy and pasted. Hence, fixing them all now might curb this practice from now on. Closes #12028 2023-10-04 17:35:54 +08:00			`</name>`
			`<command>`
tests: use %LOGDIR to refer to the log directory This will allow it be set dynamically. Ref: #10818 2023-03-29 09:20:54 +08:00			`file://%PWD/%LOGDIR/test%TESTNUMBER.txt`
test 502, multi interface with file:// 2002-12-13 21:39:39 +08:00			`</command>`
tests: use %LOGDIR to refer to the log directory This will allow it be set dynamically. Ref: #10818 2023-03-29 09:20:54 +08:00			`<file name="%LOGDIR/test%TESTNUMBER.txt">`
test 502, multi interface with file:// 2002-12-13 21:39:39 +08:00			`foo`
modified to work fine with the new persistant connection working test suite HTTP server 2003-07-20 07:57:08 +08:00			`bar swsclose`
test 502, multi interface with file:// 2002-12-13 21:39:39 +08: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-23 10:25:56 +08:00			`</testcase>`