curl/tests/data/test203

<testcase>
# Server-side
<reply>
<data>
foo
   bar
bar
   foo
moo
</data>
</reply>

# Client-side
<client>
<server>
none
</server>
 <name>
file:/path URL with a single slash
 </name>
 <command>
file:%PWD/log/test203.txt
</command>
<file name="log/test203.txt">
foo
   bar
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 02:25:56 +00:00			`<testcase>`
David Hull made the file: URL parser also accept the somewhat sloppy file syntax: file:/path. I added test case 203 to verify this. 2003-10-29 09:53:21 +00:00			`# Server-side`
			`<reply>`
			`<data>`
			`foo`
			`bar`
			`bar`
			`foo`
			`moo`
			`</data>`
			`</reply>`

			`# Client-side`
			`<client>`
			`<server>`
			`none`
			`</server>`
			`<name>`
			`file:/path URL with a single slash`
			`</name>`
			`<command>`
			`file:%PWD/log/test203.txt`
			`</command>`
			`<file name="log/test203.txt">`
			`foo`
			`bar`
			`bar`
			`foo`
			`moo`
			`</file>`
A minor "syntax error" in numerous test files corrected 2005-01-25 21:45:03 +00:00			`</client>`
David Hull made the file: URL parser also accept the somewhat sloppy file syntax: file:/path. I added test case 203 to verify this. 2003-10-29 09:53:21 +00:00
			`# 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 02:25:56 +00:00			`</testcase>`