curl/tests/data/test238

<testcase>
<info>
<keywords>
FTP
</keywords>
</info>

# Server-side
<reply>
<servercmd>
REPLY EPSV 229 Entering Passiv Mode (|||1000000|)
</servercmd>
</reply>

# Client-side
<client>
<server>
ftp
</server>
 <name>
FTP getting bad port in response to EPSV
 </name>
 <command>
ftp://%HOSTIP:%FTPPORT/238
</command>
</client>

# Verify data after the test has been "shot"
<verify>
# 13 = CURLE_FTP_WEIRD_PASV_REPLY
<errorcode>
13
</errorcode>
<protocol>
USER anonymous
PASS ftp@example.com
PWD
EPSV
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>`
Add FTP keywords for a couple of currently keyword-less FTP tests 2012-11-16 12:42:51 +01:00			`<info>`
			`<keywords>`
			`FTP`
			`</keywords>`
			`</info>`

test EPSV and PASV response handling when they get well-formated data back but using illegal values 2005-03-15 13:33:08 +01: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 22:22:01 +02:00			`<servercmd>`
			`REPLY EPSV 229 Entering Passiv Mode (\|\|\|1000000\|)`
			`</servercmd>`
test EPSV and PASV response handling when they get well-formated data back but using illegal values 2005-03-15 13:33:08 +01:00			`</reply>`

			`# Client-side`
			`<client>`
			`<server>`
			`ftp`
			`</server>`
			`<name>`
FTP: reject illegal port numbers in EPSV 229 responses 2013-01-15 22:35:48 +01:00			`FTP getting bad port in response to EPSV`
test EPSV and PASV response handling when they get well-formated data back but using illegal values 2005-03-15 13:33:08 +01:00			`</name>`
			`<command>`
			`ftp://%HOSTIP:%FTPPORT/238`
			`</command>`
			`</client>`

			`# Verify data after the test has been "shot"`
			`<verify>`
FTP: reject illegal port numbers in EPSV 229 responses 2013-01-15 22:35:48 +01:00			`# 13 = CURLE_FTP_WEIRD_PASV_REPLY`
test EPSV and PASV response handling when they get well-formated data back but using illegal values 2005-03-15 13:33:08 +01:00			`<errorcode>`
FTP: reject illegal port numbers in EPSV 229 responses 2013-01-15 22:35:48 +01:00			`13`
test EPSV and PASV response handling when they get well-formated data back but using illegal values 2005-03-15 13:33:08 +01:00			`</errorcode>`
			`<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`
test EPSV and PASV response handling when they get well-formated data back but using illegal values 2005-03-15 13:33:08 +01:00			`PWD`
			`EPSV`
FTP: reject illegal port numbers in EPSV 229 responses 2013-01-15 22:35:48 +01:00			`QUIT`
test EPSV and PASV response handling when they get well-formated data back but using illegal values 2005-03-15 13:33:08 +01: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>`