curl/tests/data/test135

<testcase>
<info>
<keywords>
FTP
EPSV
RETR
Range
</keywords>
</info>
# Server-side
<reply>
<data>
0123456789abcdef
0123456789abcdef
0123456789abcdef
0123456789abcdef
</data>
<datacheck nonewline="yes">
0123456789abc
</datacheck>
<size>
64
</size>
</reply>

# Client-side
<client>
<server>
ftp
</server>
 <name>
FTP retrieve a byte-range
 </name>
 <command>
-r 4-16 ftp://%HOSTIP:%FTPPORT/135
</command>
</client>

# Verify data after the test has been "shot"
<verify>
<protocol>
USER anonymous
PASS ftp@example.com
PWD
EPSV
TYPE I
SIZE 135
REST 4
RETR 135
QUIT
</protocol>
</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 03:25:56 +01:00			`<testcase>`
keyword update 2005-04-27 11:59:47 +02:00			`<info>`
			`<keywords>`
			`FTP`
			`EPSV`
			`RETR`
			`Range`
			`</keywords>`
			`</info>`
added test135 ftp byte-range download 2002-06-11 14:25:46 +02:00			`# Server-side`
			`<reply>`
			`<data>`
			`0123456789abcdef`
			`0123456789abcdef`
			`0123456789abcdef`
			`0123456789abcdef`
			`</data>`
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 03:25:56 +01:00			`<datacheck nonewline="yes">`
added test135 ftp byte-range download 2002-06-11 14:25:46 +02:00			`0123456789abc`
			`</datacheck>`
			`<size>`
			`64`
			`</size>`
			`</reply>`

			`# Client-side`
			`<client>`
Each test case now specifies which server(s) it needs, without relying on the test number. 2003-04-30 22:25:39 +02:00			`<server>`
			`ftp`
			`</server>`
added test135 ftp byte-range download 2002-06-11 14:25:46 +02:00			`<name>`
			`FTP retrieve a byte-range`
			`</name>`
			`<command>`
			`-r 4-16 ftp://%HOSTIP:%FTPPORT/135`
			`</command>`
A minor "syntax error" in numerous test files corrected 2005-01-25 22:45:03 +01:00			`</client>`
added test135 ftp byte-range download 2002-06-11 14:25:46 +02:00
			`# Verify data after the test has been "shot"`
			`<verify>`
			`<protocol>`
			`USER anonymous`
ftp@example.com is now the new anonymous FTP password. I opted for 'ftp' on the left side of @ to make it short(er). 2007-02-13 23:50:16 +01:00			`PASS ftp@example.com`
added test135 ftp byte-range download 2002-06-11 14:25:46 +02:00			`PWD`
			`EPSV`
			`TYPE I`
			`SIZE 135`
			`REST 4`
			`RETR 135`
Joe Halpin made the FTP code send 'QUIT' on the control connection before it disconnects the TCP connection, like a good ftp client should! 2004-02-27 08:08:37 +01:00			`QUIT`
added test135 ftp byte-range download 2002-06-11 14:25:46 +02:00			`</protocol>`
			`</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 03:25:56 +01:00			`</testcase>`