test1112 4.4 KB

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