Página inicial Explorar Ajuda
Entrar
OWEALs
/
curl
mirror de https://github.com/curl/curl.git
2
0
Fork 0
Arquivos Issues 8 Wiki
Tree: 94ac2ca775
Branches Tags
curl
/
tests
/
data
/
test1112

test1112 4.4 KB
Histórico Raw

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114 
  1. <testcase>
    2. 

  2. <info>
    3. 

  3. <keywords>
    4. 

  4. FTPS
    5. 

  5. EPSV
    6. 

  6. RETR
    7. 

  7. timeout
    8. 

  8. FAILURE
    9. 

  9. </keywords>
    10. 

  10. </info>
    11. 

  11. 

  12. # Server-side
    13. 

  13. <reply>
    14. 

  14. # Overload some standard FTP responses to make them shorter and faster
    15. 

  15. # to avoid wasting time waiting for the data phase to start
    16. 

  16. <servercmd>
    17. 

  17. SLOWDOWN
    18. 

  18. REPLY USER 331 OK
    19. 

  19. REPLY PASS 230 OK
    20. 

  20. REPLY PWD 257 "/"
    21. 

  21. REPLY TYPE 200 OK
    22. 

  22. </servercmd>
    23. 

  23. <data nocheck="yes">
    24. 

  24. Long chunk of data that couldn't possibly be sent in the time allotted.
    25. 

  25. Long chunk of data that couldn't possibly be sent in the time allotted.
    26. 

  26. Long chunk of data that couldn't possibly be sent in the time allotted.
    27. 

  27. Long chunk of data that couldn't possibly be sent in the time allotted.
    28. 

  28. Long chunk of data that couldn't possibly be sent in the time allotted.
    29. 

  29. Long chunk of data that couldn't possibly be sent in the time allotted.
    30. 

  30. Long chunk of data that couldn't possibly be sent in the time allotted.
    31. 

  31. Long chunk of data that couldn't possibly be sent in the time allotted.
    32. 

  32. Long chunk of data that couldn't possibly be sent in the time allotted.
    33. 

  33. Long chunk of data that couldn't possibly be sent in the time allotted.
    34. 

  34. Long chunk of data that couldn't possibly be sent in the time allotted.
    35. 

  35. Long chunk of data that couldn't possibly be sent in the time allotted.
    36. 

  36. Long chunk of data that couldn't possibly be sent in the time allotted.
    37. 

  37. Long chunk of data that couldn't possibly be sent in the time allotted.
    38. 

  38. Long chunk of data that couldn't possibly be sent in the time allotted.
    39. 

  39. Long chunk of data that couldn't possibly be sent in the time allotted.
    40. 

  40. Long chunk of data that couldn't possibly be sent in the time allotted.
    41. 

  41. Long chunk of data that couldn't possibly be sent in the time allotted.
    42. 

  42. Long chunk of data that couldn't possibly be sent in the time allotted.
    43. 

  43. Long chunk of data that couldn't possibly be sent in the time allotted.
    44. 

  44. Long chunk of data that couldn't possibly be sent in the time allotted.
    45. 

  45. Long chunk of data that couldn't possibly be sent in the time allotted.
    46. 

  46. Long chunk of data that couldn't possibly be sent in the time allotted.
    47. 

  47. Long chunk of data that couldn't possibly be sent in the time allotted.
    48. 

  48. Long chunk of data that couldn't possibly be sent in the time allotted.
    49. 

  49. Long chunk of data that couldn't possibly be sent in the time allotted.
    50. 

  50. Long chunk of data that couldn't possibly be sent in the time allotted.
    51. 

  51. Long chunk of data that couldn't possibly be sent in the time allotted.
    52. 

  52. Long chunk of data that couldn't possibly be sent in the time allotted.
    53. 

  53. Long chunk of data that couldn't possibly be sent in the time allotted.
    54. 

  54. Long chunk of data that couldn't possibly be sent in the time allotted.
    55. 

  55. Long chunk of data that couldn't possibly be sent in the time allotted.
    56. 

  56. Long chunk of data that couldn't possibly be sent in the time allotted.
    57. 

  57. Long chunk of data that couldn't possibly be sent in the time allotted.
    58. 

  58. Long chunk of data that couldn't possibly be sent in the time allotted.
    59. 

  59. Long chunk of data that couldn't possibly be sent in the time allotted.
    60. 

  60. Long chunk of data that couldn't possibly be sent in the time allotted.
    61. 

  61. Long chunk of data that couldn't possibly be sent in the time allotted.
    62. 

  62. Long chunk of data that couldn't possibly be sent in the time allotted.
    63. 

  63. Long chunk of data that couldn't possibly be sent in the time allotted.
    64. 

  64. Long chunk of data that couldn't possibly be sent in the time allotted.
    65. 

  65. Long chunk of data that couldn't possibly be sent in the time allotted.
    66. 

  66. Long chunk of data that couldn't possibly be sent in the time allotted.
    67. 

  67. Long chunk of data that couldn't possibly be sent in the time allotted.
    68. 

  68. Long chunk of data that couldn't possibly be sent in the time allotted.
    69. 

  69. Long chunk of data that couldn't possibly be sent in the time allotted.
    70. 

  70. Long chunk of data that couldn't possibly be sent in the time allotted.
    71. 

  71. Long chunk of data that couldn't possibly be sent in the time allotted.
    72. 

  72. Long chunk of data that couldn't possibly be sent in the time allotted.
    73. 

  73. Long chunk of data that couldn't possibly be sent in the time allotted.
    74. 

  74. </data>
    75. 

  75. </reply>
    76. 

  76. 

  77. # Client-side
    78. 

  78. <client>
    79. 

  79. <features>
    80. 

  80. SSL
    81. 

  81. </features>
    82. 

  82. <server>
    83. 

  83. ftps
    84. 

  84. </server>
    85. 

  85. <killserver>
    86. 

  86. ftps
    87. 

  87. </killserver>
    88. 

  88.  <name>
    89. 

  89. FTPS download with strict timeout and slow data transfer
    90. 

  90.  </name>
    91. 

  91.  <command timeout="1">
    92. 

  92. -k --ftp-ssl-control ftps://%HOSTIP:%FTPSPORT/%TESTNUMBER -m 16
    93. 

  93. </command>
    94. 

  94. </client>
    95. 

  95. 

  96. # Verify data after the test has been "shot"
    97. 

  97. <verify>
    98. 

  98. # 28 is CURLE_OPERATION_TIMEDOUT
    99. 

  99. <errorcode>
    100. 

  100. 28
    101. 

  101. </errorcode>
    102. 

  102. <protocol>
    103. 

  103. USER anonymous
    104. 

  104. PASS ftp@example.com
    105. 

  105. PBSZ 0
    106. 

  106. PROT C
    107. 

  107. PWD
    108. 

  108. EPSV
    109. 

  109. TYPE I
    110. 

  110. SIZE %TESTNUMBER
    111. 

  111. RETR %TESTNUMBER
    112. 

  112. </protocol>
    113. 

  113. </verify>
    114. 

  114. </testcase>
    115.