curl/tests/data/test261

<testcase>
<info>
<keywords>
FTP
EPSV
RETR
</keywords>
</info>
#
# Server-side
<reply>
<data>
hepp
</data>
<servercmd>
REPLY TYPE 226 Kind of on the positive side!
</servercmd>
</reply>

#
# Client-side
<client>
<server>
ftp
</server>
<name>
FTP RETR with 226 response code to TYPE
</name>
<command>
ftp://%HOSTIP:%FTPPORT/%TESTNUMBER
</command>
</client>

#
# Verify data after the test has been "shot"
<verify>
<protocol>
USER anonymous
PASS ftp@example.com
PWD
EPSV
TYPE I
SIZE %TESTNUMBER
RETR %TESTNUMBER
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 10:25:56 +08:00			`<testcase>`
add test case 261, response code 226 to TYPE 2005-05-24 17:40:58 +08:00			`<info>`
			`<keywords>`
			`FTP`
			`EPSV`
			`RETR`
			`</keywords>`
			`</info>`
			`#`
			`# Server-side`
			`<reply>`
			`<data>`
			`hepp`
			`</data>`
			`<servercmd>`
			`REPLY TYPE 226 Kind of on the positive side!`
			`</servercmd>`
			`</reply>`

			`#`
			`# Client-side`
			`<client>`
			`<server>`
			`ftp`
			`</server>`
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>`
add test case 261, response code 226 to TYPE 2005-05-24 17:40:58 +08:00			`FTP RETR with 226 response code to TYPE`
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 %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			`ftp://%HOSTIP:%FTPPORT/%TESTNUMBER`
add test case 261, response code 226 to TYPE 2005-05-24 17:40:58 +08:00			`</command>`
			`</client>`

			`#`
			`# 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-14 06:50:16 +08:00			`PASS ftp@example.com`
add test case 261, response code 226 to TYPE 2005-05-24 17:40:58 +08:00			`PWD`
			`EPSV`
			`TYPE I`
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			`SIZE %TESTNUMBER`
			`RETR %TESTNUMBER`
add test case 261, response code 226 to TYPE 2005-05-24 17:40:58 +08:00			`QUIT`
			`</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 10:25:56 +08:00			`</testcase>`