curl/tests/data/test238

<testcase>
# Server-side
<reply>
</reply>

# Client-side
<client>
<server>
ftp
</server>
 <name>
FTP getting bad port in response to EPSV and in response to PASV
 </name>
 <command>
ftp://%HOSTIP:%FTPPORT/238
</command>
<file name="log/ftpserver.cmd">
REPLY EPSV 229 Entering Passiv Mode (|||1000000|)
REPLY PASV 227 Entering Passiv Mode (1216,256,2,127,127,127)
</file>
</client>

# Verify data after the test has been "shot"
<verify>
# curl: (15) Can't resolve new host 1216.256.2.127:32639
# 15 => CURLE_FTP_CANT_GET_HOST
# some systems just don't fail on the illegal host name/address but instead
# moves on and attempt to connect to... yes, to what?
# 7= CURLE_COULDNT_CONNECT
<errorcode>
7, 15
</errorcode>
<protocol>
USER anonymous
PASS ftp@example.com
PWD
EPSV
PASV
</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>`
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>`
			`</reply>`

			`# Client-side`
			`<client>`
			`<server>`
			`ftp`
			`</server>`
			`<name>`
Michal Marek provided a patch for FTP that makes libcurl continue to try PASV even after EPSV returned a positive response code, if libcurl failed to connect to the port number the EPSV response said. Obviously some people are going through protocol-sensitive firewalls (or similar) that don't understand EPSV and then they don't allow the second connection unless PASV was used. This also called for a minor fix of test case 238. 2006-01-24 15:40:43 +01:00			`FTP getting bad port in response to EPSV and in response to PASV`
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>`
			`<file name="log/ftpserver.cmd">`
			`REPLY EPSV 229 Entering Passiv Mode (\|\|\|1000000\|)`
Michal Marek provided a patch for FTP that makes libcurl continue to try PASV even after EPSV returned a positive response code, if libcurl failed to connect to the port number the EPSV response said. Obviously some people are going through protocol-sensitive firewalls (or similar) that don't understand EPSV and then they don't allow the second connection unless PASV was used. This also called for a minor fix of test case 238. 2006-01-24 15:40:43 +01:00			`REPLY PASV 227 Entering Passiv Mode (1216,256,2,127,127,127)`
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			`</file>`
			`</client>`

			`# Verify data after the test has been "shot"`
			`<verify>`
Michal Marek provided a patch for FTP that makes libcurl continue to try PASV even after EPSV returned a positive response code, if libcurl failed to connect to the port number the EPSV response said. Obviously some people are going through protocol-sensitive firewalls (or similar) that don't understand EPSV and then they don't allow the second connection unless PASV was used. This also called for a minor fix of test case 238. 2006-01-24 15:40:43 +01:00			`# curl: (15) Can't resolve new host 1216.256.2.127:32639`
			`# 15 => CURLE_FTP_CANT_GET_HOST`
			`# some systems just don't fail on the illegal host name/address but instead`
			`# moves on and attempt to connect to... yes, to what?`
			`# 7= CURLE_COULDNT_CONNECT`
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>`
Michal Marek provided a patch for FTP that makes libcurl continue to try PASV even after EPSV returned a positive response code, if libcurl failed to connect to the port number the EPSV response said. Obviously some people are going through protocol-sensitive firewalls (or similar) that don't understand EPSV and then they don't allow the second connection unless PASV was used. This also called for a minor fix of test case 238. 2006-01-24 15:40:43 +01:00			`7, 15`
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`
Michal Marek provided a patch for FTP that makes libcurl continue to try PASV even after EPSV returned a positive response code, if libcurl failed to connect to the port number the EPSV response said. Obviously some people are going through protocol-sensitive firewalls (or similar) that don't understand EPSV and then they don't allow the second connection unless PASV was used. This also called for a minor fix of test case 238. 2006-01-24 15:40:43 +01:00			`PASV`
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>`