| 1 |
# Server-side |
| 2 |
<reply> |
| 3 |
</reply> |
| 4 |
|
| 5 |
# Client-side |
| 6 |
<client> |
| 7 |
<server> |
| 8 |
ftp |
| 9 |
</server> |
| 10 |
<name> |
| 11 |
FTP getting bad host in 227-response to PASV |
| 12 |
</name> |
| 13 |
<command> |
| 14 |
ftp://%HOSTIP:%FTPPORT/237 --disable-epsv |
| 15 |
</command> |
| 16 |
<file name="log/ftpserver.cmd"> |
| 17 |
REPLY PASV 227 Entering Passiv Mode (1216,256,2,127,127,127) |
| 18 |
</file> |
| 19 |
</client> |
| 20 |
|
| 21 |
# Verify data after the test has been "shot" |
| 22 |
# The bogus address used here is chosen specifically so that when processed on |
| 23 |
# certain hosts with buggy resolver code, the resulting address (192.0.2.127) |
| 24 |
# is from an address block that is guaranteed never to be assigned (RFC3330). |
| 25 |
<verify> |
| 26 |
# curl: (15) Can't resolve new host 1216.256.2.127:32639 |
| 27 |
# 15 => CURLE_FTP_CANT_GET_HOST |
| 28 |
# some systems just don't fail on the illegal host name/address but instead |
| 29 |
# moves on and attempt to connect to... yes, to what? |
| 30 |
# 7= CURLE_COULDNT_CONNECT |
| 31 |
<errorcode> |
| 32 |
15, 7 |
| 33 |
</errorcode> |
| 34 |
<protocol> |
| 35 |
USER anonymous |
| 36 |
PASS [email protected] |
| 37 |
PWD |
| 38 |
PASV |
| 39 |
</protocol> |
| 40 |
</verify> |