Home | History | Annotate | Download | only in data 
      1 <testcase>
      2 <info>
      3 <keywords>
      4 FTP
      5 EPSV
      6 RETR
      7 timeout
      8 FAILURE
      9 flaky
     10 </keywords>
     11 </info>
     12 
     13 # Server-side
     14 <reply>
     15 # Overload some standard FTP responses to make them shorter and faster
     16 # to avoid wasting time waiting for the data phase to start
     17 <servercmd>
     18 SLOWDOWN
     19 REPLY USER 331 OK
     20 REPLY PASS 230 OK
     21 REPLY PWD 257 "/"
     22 REPLY TYPE 200 OK
     23 </servercmd>
     24 <data nocheck="yes">
     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 Long chunk of data that couldn't possibly be sent in the time allotted.
     75 </data>
     76 </reply>
     77 
     78 # Client-side
     79 <client>
     80 <server>
     81 ftp
     82 </server>
     83 <killserver>
     84 ftp
     85 </killserver>
     86  <name>
     87 FTP download with strict timeout and slow data transfer
     88  </name>
     89  <command timeout="1">
     90 ftp://%HOSTIP:%FTPPORT/1086 -m 7
     91 </command>
     92 </client>
     93 
     94 # Verify data after the test has been "shot"
     95 <verify>
     96 # 28 is CURLE_OPERATION_TIMEDOUT
     97 <errorcode>
     98 28
     99 </errorcode>
    100 <protocol>
    101 USER anonymous
    102 PASS ftp (a] example.com
    103 PWD
    104 EPSV
    105 TYPE I
    106 SIZE 1086
    107 RETR 1086
    108 </protocol>
    109 </verify>
    110 </testcase>
    111