| lh | 9ed821d | 2023-04-07 01:36:19 -0700 | [diff] [blame] | 1 | <testcase> |
| 2 | <info> |
| 3 | <keywords> |
| 4 | FTPS |
| 5 | EPSV |
| 6 | RETR |
| 7 | timeout |
| 8 | FAILURE |
| 9 | </keywords> |
| 10 | </info> |
| 11 | |
| 12 | # Server-side |
| 13 | <reply> |
| 14 | # Overload some standard FTP responses to make them shorter and faster |
| 15 | # to avoid wasting time waiting for the data phase to start |
| 16 | <servercmd> |
| 17 | SLOWDOWN |
| 18 | REPLY USER 331 OK |
| 19 | REPLY PASS 230 OK |
| 20 | REPLY PWD 257 "/" |
| 21 | REPLY TYPE 200 OK |
| 22 | </servercmd> |
| 23 | <data nocheck="yes"> |
| 24 | Long chunk of data that couldn't possibly be sent in the time allotted. |
| 25 | Long chunk of data that couldn't possibly be sent in the time allotted. |
| 26 | Long chunk of data that couldn't possibly be sent in the time allotted. |
| 27 | Long chunk of data that couldn't possibly be sent in the time allotted. |
| 28 | Long chunk of data that couldn't possibly be sent in the time allotted. |
| 29 | Long chunk of data that couldn't possibly be sent in the time allotted. |
| 30 | Long chunk of data that couldn't possibly be sent in the time allotted. |
| 31 | Long chunk of data that couldn't possibly be sent in the time allotted. |
| 32 | Long chunk of data that couldn't possibly be sent in the time allotted. |
| 33 | Long chunk of data that couldn't possibly be sent in the time allotted. |
| 34 | Long chunk of data that couldn't possibly be sent in the time allotted. |
| 35 | Long chunk of data that couldn't possibly be sent in the time allotted. |
| 36 | Long chunk of data that couldn't possibly be sent in the time allotted. |
| 37 | Long chunk of data that couldn't possibly be sent in the time allotted. |
| 38 | Long chunk of data that couldn't possibly be sent in the time allotted. |
| 39 | Long chunk of data that couldn't possibly be sent in the time allotted. |
| 40 | Long chunk of data that couldn't possibly be sent in the time allotted. |
| 41 | Long chunk of data that couldn't possibly be sent in the time allotted. |
| 42 | Long chunk of data that couldn't possibly be sent in the time allotted. |
| 43 | Long chunk of data that couldn't possibly be sent in the time allotted. |
| 44 | Long chunk of data that couldn't possibly be sent in the time allotted. |
| 45 | Long chunk of data that couldn't possibly be sent in the time allotted. |
| 46 | Long chunk of data that couldn't possibly be sent in the time allotted. |
| 47 | Long chunk of data that couldn't possibly be sent in the time allotted. |
| 48 | Long chunk of data that couldn't possibly be sent in the time allotted. |
| 49 | Long chunk of data that couldn't possibly be sent in the time allotted. |
| 50 | Long chunk of data that couldn't possibly be sent in the time allotted. |
| 51 | Long chunk of data that couldn't possibly be sent in the time allotted. |
| 52 | Long chunk of data that couldn't possibly be sent in the time allotted. |
| 53 | Long chunk of data that couldn't possibly be sent in the time allotted. |
| 54 | Long chunk of data that couldn't possibly be sent in the time allotted. |
| 55 | Long chunk of data that couldn't possibly be sent in the time allotted. |
| 56 | Long chunk of data that couldn't possibly be sent in the time allotted. |
| 57 | Long chunk of data that couldn't possibly be sent in the time allotted. |
| 58 | Long chunk of data that couldn't possibly be sent in the time allotted. |
| 59 | Long chunk of data that couldn't possibly be sent in the time allotted. |
| 60 | Long chunk of data that couldn't possibly be sent in the time allotted. |
| 61 | Long chunk of data that couldn't possibly be sent in the time allotted. |
| 62 | Long chunk of data that couldn't possibly be sent in the time allotted. |
| 63 | Long chunk of data that couldn't possibly be sent in the time allotted. |
| 64 | Long chunk of data that couldn't possibly be sent in the time allotted. |
| 65 | Long chunk of data that couldn't possibly be sent in the time allotted. |
| 66 | Long chunk of data that couldn't possibly be sent in the time allotted. |
| 67 | Long chunk of data that couldn't possibly be sent in the time allotted. |
| 68 | Long chunk of data that couldn't possibly be sent in the time allotted. |
| 69 | Long chunk of data that couldn't possibly be sent in the time allotted. |
| 70 | Long chunk of data that couldn't possibly be sent in the time allotted. |
| 71 | Long chunk of data that couldn't possibly be sent in the time allotted. |
| 72 | Long chunk of data that couldn't possibly be sent in the time allotted. |
| 73 | Long chunk of data that couldn't possibly be sent in the time allotted. |
| 74 | </data> |
| 75 | </reply> |
| 76 | |
| 77 | # Client-side |
| 78 | <client> |
| 79 | <features> |
| 80 | SSL |
| 81 | </features> |
| 82 | <server> |
| 83 | ftps |
| 84 | </server> |
| 85 | <killserver> |
| 86 | ftps |
| 87 | </killserver> |
| 88 | <name> |
| 89 | FTPS download with strict timeout and slow data transfer |
| 90 | </name> |
| 91 | <command timeout="1"> |
| 92 | -k --ftp-ssl-control ftps://%HOSTIP:%FTPSPORT/1112 -m 16 |
| 93 | </command> |
| 94 | </client> |
| 95 | |
| 96 | # Verify data after the test has been "shot" |
| 97 | <verify> |
| 98 | # 28 is CURLE_OPERATION_TIMEDOUT |
| 99 | <errorcode> |
| 100 | 28 |
| 101 | </errorcode> |
| 102 | <protocol> |
| 103 | USER anonymous
|
| 104 | PASS ftp@example.com
|
| 105 | PBSZ 0
|
| 106 | PROT C
|
| 107 | PWD
|
| 108 | EPSV
|
| 109 | TYPE I
|
| 110 | SIZE 1112
|
| 111 | RETR 1112
|
| 112 | </protocol> |
| 113 | </verify> |
| 114 | </testcase> |