quickjs-tart

quickjs-based runtime for wallet-core logic
Log | Files | Refs | README | LICENSE

test1112 (4496B)


      1 <testcase>
      2 # This is the ftps equivalent of test1086
      3 <info>
      4 <keywords>
      5 FTPS
      6 EPSV
      7 RETR
      8 timeout
      9 FAILURE
     10 SLOWDOWNDATA
     11 timing-dependent
     12 </keywords>
     13 </info>
     14 
     15 # Server-side
     16 <reply>
     17 <servercmd>
     18 SLOWDOWNDATA
     19 REPLY welcome 220 Hey
     20 REPLY USER 331 OK
     21 REPLY PASS 230 OK
     22 REPLY PWD 257 "/"
     23 REPLY TYPE 200 OK
     24 </servercmd>
     25 <data nocheck="yes">
     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 Long chunk of data that couldn't possibly be sent in the time allotted.
     76 </data>
     77 </reply>
     78 
     79 # Client-side
     80 <client>
     81 <features>
     82 SSL
     83 </features>
     84 <server>
     85 ftps
     86 </server>
     87 <killserver>
     88 ftps
     89 </killserver>
     90 <name>
     91 FTPS download with strict timeout and slow data transfer
     92 </name>
     93 <command>
     94 --insecure --ftp-ssl-control ftps://%HOSTIP:%FTPSPORT/%TESTNUMBER -m 5
     95 </command>
     96 </client>
     97 
     98 # Verify data after the test has been "shot"
     99 <verify>
    100 # 28 is CURLE_OPERATION_TIMEDOUT
    101 <errorcode>
    102 28
    103 </errorcode>
    104 <protocol>
    105 USER anonymous
    106 PASS ftp@example.com
    107 PBSZ 0
    108 PROT C
    109 PWD
    110 EPSV
    111 TYPE I
    112 SIZE %TESTNUMBER
    113 RETR %TESTNUMBER
    114 </protocol>
    115 </verify>
    116 </testcase>