curl/tests/data/test145

<testcase>
<info>
<keywords>
FTP
NLST
PORT
</keywords>
</info>
# Server-side
<reply>
<servercmd>
REPLY NLST 550 Have a taste on this!
</servercmd>
<data>
</data>
</reply>

# Client-side
<client>
<server>
ftp
</server>
 <name>
FTP NLST dir list with weird reply code, using PORT
 </name>
 <command>
ftp://%HOSTIP:%FTPPORT/ -P - -l
</command>
</client>

# Verify data after the test has been "shot"
<verify>
<errorcode>
19
</errorcode>
# Strip all valid kinds of PORT and EPRT that curl can send
<strip>
^PORT \d{1,3},\d{1,3},\d{1,3},\d{1,3},\d{1,3},\d{1,3}
^EPRT \|1\|\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}\|\d{1,5}\|
</strip>
<protocol>
USER anonymous
PASS ftp@example.com
PWD
PORT 127,0,0,1,243,212
TYPE A
NLST
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-22 21:25:56 -05:00			`<testcase>`
add keywords 2007-12-08 17:56:17 -05:00			`<info>`
			`<keywords>`
			`FTP`
			`NLST`
			`PORT`
			`</keywords>`
			`</info>`
more ftp testing using NLST and no contents and bad return code 2003-05-23 07:10:35 -04:00			`# Server-side`
			`<reply>`
Various test file cleanups, including using <servercmd> instead of writing directly to ftpserver.cmd and removing unneeded empty sections. 2007-04-18 16:22:01 -04:00			`<servercmd>`
			`REPLY NLST 550 Have a taste on this!`
			`</servercmd>`
more ftp testing using NLST and no contents and bad return code 2003-05-23 07:10:35 -04:00			`<data>`
			`</data>`
			`</reply>`

			`# Client-side`
			`<client>`
			`<server>`
			`ftp`
			`</server>`
			`<name>`
			`FTP NLST dir list with weird reply code, using PORT`
			`</name>`
			`<command>`
			`ftp://%HOSTIP:%FTPPORT/ -P - -l`
			`</command>`
A minor "syntax error" in numerous test files corrected 2005-01-25 16:45:03 -05:00			`</client>`
more ftp testing using NLST and no contents and bad return code 2003-05-23 07:10:35 -04:00
			`# Verify data after the test has been "shot"`
			`<verify>`
			`<errorcode>`
			`19`
			`</errorcode>`
Changed some FTP tests to validate the format of the PORT and EPRT commands sent by curl, if not the addresses themselves. 2007-09-17 17:44:57 -04:00			`# Strip all valid kinds of PORT and EPRT that curl can send`
more ftp testing using NLST and no contents and bad return code 2003-05-23 07:10:35 -04:00			`<strip>`
Changed some FTP tests to validate the format of the PORT and EPRT commands sent by curl, if not the addresses themselves. 2007-09-17 17:44:57 -04:00			`^PORT \d{1,3},\d{1,3},\d{1,3},\d{1,3},\d{1,3},\d{1,3}`
			`^EPRT \\|1\\|\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}\\|\d{1,5}\\|`
more ftp testing using NLST and no contents and bad return code 2003-05-23 07:10:35 -04:00			`</strip>`
			`<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 17:50:16 -05:00			`PASS ftp@example.com`
more ftp testing using NLST and no contents and bad return code 2003-05-23 07:10:35 -04:00			`PWD`
			`PORT 127,0,0,1,243,212`
			`TYPE A`
			`NLST`
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 02:08:37 -05:00			`QUIT`
more ftp testing using NLST and no contents and bad return code 2003-05-23 07:10:35 -04: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-22 21:25:56 -05:00			`</testcase>`