curl/tests/data/test116

<testcase>
<info>
<keywords>
FTP
PORT
FAILURE
</keywords>
</info>
# Server-side
<reply>
<servercmd>
REPLY PORT 314 bluah you f00l!
</servercmd>
</reply>

# Client-side
<client>
<server>
ftp
</server>
# EPRT is only sent when IPv6 is enabled
<features>
ipv6
</features>
 <name>
FTP download, failed PORT
 </name>
 <command>
ftp://%HOSTIP:%FTPPORT/116 -P 1.2.3.4
</command>
</client>

# Verify data after the test has been "shot"
<verify>
<errorcode>
30
</errorcode>
# Strip the port number but leave the rest
<strippart>
s/^(PORT \d{1,3},\d{1,3},\d{1,3},\d{1,3},)\d{1,3},\d{1,3}/$1/
s/^(EPRT \|1\|\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}\|)\d{1,5}\|/$1/
</strippart>
<protocol>
USER anonymous
PASS ftp@example.com
PWD
EPRT |1|1.2.3.4|
PORT 1,2,3,4,
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>`
keyword update 2005-04-27 05:59:47 -04:00			`<info>`
			`<keywords>`
			`FTP`
			`PORT`
			`FAILURE`
			`</keywords>`
			`</info>`
new FTP tests 2001-09-14 08:03:33 -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 PORT 314 bluah you f00l!`
			`</servercmd>`
new FTP tests 2001-09-14 08:03:33 -04:00			`</reply>`

			`# Client-side`
			`<client>`
Each test case now specifies which server(s) it needs, without relying on the test number. 2003-04-30 16:25:39 -04:00			`<server>`
			`ftp`
			`</server>`
IPv6 is a required feature for these two tests, even if it's not obvious. 2007-09-18 13:41:04 -04:00			`# EPRT is only sent when IPv6 is enabled`
			`<features>`
			`ipv6`
			`</features>`
new FTP tests 2001-09-14 08:03:33 -04:00			`<name>`
			`FTP download, failed PORT`
			`</name>`
			`<command>`
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			`ftp://%HOSTIP:%FTPPORT/116 -P 1.2.3.4`
new FTP tests 2001-09-14 08:03:33 -04:00			`</command>`
A minor "syntax error" in numerous test files corrected 2005-01-25 16:45:03 -05:00			`</client>`
new FTP tests 2001-09-14 08:03:33 -04:00
			`# Verify data after the test has been "shot"`
			`<verify>`
			`<errorcode>`
			`30`
			`</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 the port number but leave the rest`
			`<strippart>`
			`s/^(PORT \d{1,3},\d{1,3},\d{1,3},\d{1,3},)\d{1,3},\d{1,3}/$1/`
			`s/^(EPRT \\|1\\|\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}\\|)\d{1,5}\\|/$1/`
			`</strippart>`
new FTP tests 2001-09-14 08:03:33 -04:00			`<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`
new FTP tests 2001-09-14 08:03:33 -04:00			`PWD`
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			`EPRT \|1\|1.2.3.4\|`
			`PORT 1,2,3,4,`
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`
new FTP tests 2001-09-14 08:03:33 -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>`