2007-01-23 10:25:56 +08:00
|
|
|
<testcase>
|
2012-11-16 19:42:51 +08:00
|
|
|
<info>
|
|
|
|
|
<keywords>
|
|
|
|
|
FTP
|
|
|
|
|
</keywords>
|
|
|
|
|
</info>
|
|
|
|
|
|
2005-03-15 20:33:08 +08:00
|
|
|
# Server-side
|
|
|
|
|
<reply>
|
2007-04-19 04:22:01 +08:00
|
|
|
<servercmd>
|
|
|
|
|
REPLY PASV 227 Entering Passiv Mode (1216,256,2,127,127,127)
|
|
|
|
|
</servercmd>
|
2005-03-15 20:33:08 +08:00
|
|
|
</reply>
|
|
|
|
|
|
|
|
|
|
# Client-side
|
|
|
|
|
<client>
|
|
|
|
|
<server>
|
|
|
|
|
ftp
|
|
|
|
|
</server>
|
|
|
|
|
<name>
|
|
|
|
|
FTP getting bad host in 227-response to PASV
|
|
|
|
|
</name>
|
|
|
|
|
<command>
|
|
|
|
|
ftp://%HOSTIP:%FTPPORT/237 --disable-epsv
|
|
|
|
|
</command>
|
|
|
|
|
</client>
|
|
|
|
|
|
|
|
|
|
# Verify data after the test has been "shot"
|
2005-03-18 04:50:17 +08:00
|
|
|
# The bogus address used here is chosen specifically so that when processed on
|
|
|
|
|
# certain hosts with buggy resolver code, the resulting address (192.0.2.127)
|
|
|
|
|
# is from an address block that is guaranteed never to be assigned (RFC3330).
|
2005-03-15 20:33:08 +08:00
|
|
|
<verify>
|
2005-03-18 04:50:17 +08:00
|
|
|
# curl: (15) Can't resolve new host 1216.256.2.127:32639
|
2005-03-15 20:33:08 +08:00
|
|
|
# 15 => CURLE_FTP_CANT_GET_HOST
|
2005-03-17 16:17:48 +08:00
|
|
|
# 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
|
2005-03-15 20:33:08 +08:00
|
|
|
<errorcode>
|
2005-03-17 16:17:48 +08:00
|
|
|
15, 7
|
2005-03-15 20:33:08 +08:00
|
|
|
</errorcode>
|
|
|
|
|
<protocol>
|
|
|
|
|
USER anonymous
|
2007-02-14 06:50:16 +08:00
|
|
|
PASS ftp@example.com
|
2005-03-15 20:33:08 +08:00
|
|
|
PWD
|
|
|
|
|
PASV
|
|
|
|
|
</protocol>
|
|
|
|
|
</verify>
|
2007-01-23 10:25:56 +08:00
|
|
|
</testcase>
|
