| xf.li | 6c8fc1e | 2023-08-12 00:11:09 -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/%TESTNUMBER --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 | # 14 = CURLE_FTP_WEIRD_227_FORMAT |
| 34 | <errorcode> |
| 35 | 14 |
| 36 | </errorcode> |
| 37 | <protocol> |
| 38 | USER anonymous
|
| 39 | PASS ftp@example.com
|
| 40 | PWD
|
| 41 | PASV
|
| 42 | </protocol> |
| 43 | </verify> |
| 44 | </testcase> |