Home Esplora Aiuto
Accedi
OWEALs
/
curl
mirror da https://github.com/curl/curl.git
2
0
Forka 0
File Problemi 8 Wiki
Albero (Tree): 9dc0baf5c6
Rami (Branch) Tag
curl
/
tests
/
data
/
test1086

test1086 4.4 KB
Cronologia Originale

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110 
  1. <testcase>
    2. 

  2. <info>
    3. 

  3. <keywords>
    4. 

  4. FTP
    5. 

  5. EPSV
    6. 

  6. RETR
    7. 

  7. timeout
    8. 

  8. FAILURE
    9. 

  9. flaky
    10. 

  10. </keywords>
    11. 

  11. </info>
    12. 

  12. 

  13. # Server-side
    14. 

  14. <reply>
    15. 

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

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

  17. <servercmd>
    18. 

  18. SLOWDOWN
    19. 

  19. REPLY USER 331 OK
    20. 

  20. REPLY PASS 230 OK
    21. 

  21. REPLY PWD 257 "/"
    22. 

  22. REPLY TYPE 200 OK
    23. 

  23. </servercmd>
    24. 

  24. <data nocheck="yes">
    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. Long chunk of data that couldn't possibly be sent in the time allotted.
    75. 

  75. </data>
    76. 

  76. </reply>
    77. 

  77. 

  78. # Client-side
    79. 

  79. <client>
    80. 

  80. <server>
    81. 

  81. ftp
    82. 

  82. </server>
    83. 

  83. <killserver>
    84. 

  84. ftp
    85. 

  85. </killserver>
    86. 

  86.  <name>
    87. 

  87. FTP download with strict timeout and slow data transfer
    88. 

  88.  </name>
    89. 

  89.  <command timeout="1">
    90. 

  90. ftp://%HOSTIP:%FTPPORT/%TESTNUMBER -m 7
    91. 

  91. </command>
    92. 

  92. </client>
    93. 

  93. 

  94. # Verify data after the test has been "shot"
    95. 

  95. <verify>
    96. 

  96. # 28 is CURLE_OPERATION_TIMEDOUT
    97. 

  97. <errorcode>
    98. 

  98. 28
    99. 

  99. </errorcode>
    100. 

  100. <protocol>
    101. 

  101. USER anonymous
    102. 

  102. PASS ftp@example.com
    103. 

  103. PWD
    104. 

  104. EPSV
    105. 

  105. TYPE I
    106. 

  106. SIZE %TESTNUMBER
    107. 

  107. RETR %TESTNUMBER
    108. 

  108. </protocol>
    109. 

  109. </verify>
    110. 

  110. </testcase>
    111.