curl/tests/data/test231

<testcase>
<info>
<keywords>
FILE
</keywords>
</info>

# Server-side
<reply>
# 16 bytes to check
<datacheck>
B01234567
C01234567
</datacheck>
</reply>

# Client-side
<client>
<server>
file
</server>
 <name>
file:// with resume
 </name>
 <command>
file://localhost/%PWD/log/test231.txt -C 10
</command>
<file name="log/test231.txt">
A01234567
B01234567
C01234567
</file>
</client>

# Verify data after the test has been "shot"
<verify>
</verify>
</testcase>
Dmitriy Sergeyev reported a regression: resumed file:// transfers broke after 7.16.2. This is much due to the different treatment file:// gets internally, but now I added test 231 to make it less likely to happen again without us noticing! 2007-08-02 10:09:08 -04:00			`<testcase>`
tests: add keywords for a couple of FILE tests 2012-11-20 07:51:25 -05:00			`<info>`
			`<keywords>`
			`FILE`
			`</keywords>`
			`</info>`

Dmitriy Sergeyev reported a regression: resumed file:// transfers broke after 7.16.2. This is much due to the different treatment file:// gets internally, but now I added test 231 to make it less likely to happen again without us noticing! 2007-08-02 10:09:08 -04:00			`# Server-side`
			`<reply>`
			`# 16 bytes to check`
			`<datacheck>`
			`B01234567`
			`C01234567`
			`</datacheck>`
			`</reply>`

			`# Client-side`
			`<client>`
			`<server>`
			`file`
			`</server>`
			`<name>`
			`file:// with resume`
			`</name>`
			`<command>`
test231: fix wrong -C use! 2012-07-10 17:20:05 -04:00			`file://localhost/%PWD/log/test231.txt -C 10`
Dmitriy Sergeyev reported a regression: resumed file:// transfers broke after 7.16.2. This is much due to the different treatment file:// gets internally, but now I added test 231 to make it less likely to happen again without us noticing! 2007-08-02 10:09:08 -04:00			`</command>`
			`<file name="log/test231.txt">`
			`A01234567`
			`B01234567`
			`C01234567`
			`</file>`
			`</client>`

			`# Verify data after the test has been "shot"`
			`<verify>`
			`</verify>`
			`</testcase>`