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