curl/tests/data/test205

<testcase>
# no Server-side

# Client-side
<client>
<server>
none
</server>
 <name>
"upload" with file://
 </name>
 <command>
file://localhost/%PWD/log/nonexisting/result205.txt -T log/upload205.txt
</command>
<file name="log/upload205.txt">
data
in
file
to
write
</file>
</client>

# Verify data after the test has been "shot"
<verify>
# 23 => CURLE_WRITE_ERROR
<errorcode>
23
</errorcode>
</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>`
initial support for "uploading" to file:// URLs 2004-05-26 05:47:29 +08:00			`# no Server-side`

			`# Client-side`
			`<client>`
			`<server>`
			`none`
			`</server>`
			`<name>`
			`"upload" with file://`
			`</name>`
			`<command>`
			`file://localhost/%PWD/log/nonexisting/result205.txt -T log/upload205.txt`
			`</command>`
			`<file name="log/upload205.txt">`
			`data`
			`in`
			`file`
			`to`
			`write`
			`</file>`
			`</client>`

			`# Verify data after the test has been "shot"`
			`<verify>`
			`# 23 => CURLE_WRITE_ERROR`
			`<errorcode>`
			`23`
			`</errorcode>`
			`</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>`