zhaobu
/
zhujimajiang_redis
1
0
Форкнуть 0
Код Задачи 0 Pull Request'ы 0 Релизы 0 Вики Активность
诸暨麻将添加redis
Вы не можете выбрать более 25 тем Темы должны начинаться с буквы или цифры, могут содержать дефисы(-) и должны содержать не более 35 символов.
6 коммитов
2 Ветки
57 MiB
 
 
 
 
 
 
Дерево: 522a9556dd
Ветки Теги
${ item.name }
Создать ветку ${ searchTerm }
из '522a9556dd'
${ noResults }
zhujimajiang_redis/俱乐部/Source/ServerControl/curl-7.32.0/tests/data/test1086

110 строки
4.3 KiB
Исходник Вина История 

  1. <testcase>

  2. <info>

  3. <keywords>

  4. FTP

  5. EPSV

  6. RETR

  7. timeout

  8. FAILURE

  9. </keywords>

  10. </info>

  11. 

  12. # Server-side

  13. <reply>

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

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

  16. <servercmd>

  17. SLOWDOWN

  18. REPLY USER 331 OK

  19. REPLY PASS 230 OK

  20. REPLY PWD 257 "/"

  21. REPLY TYPE 200 OK

  22. </servercmd>

  23. <data nocheck="yes">

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

  74. </data>

  75. </reply>

  76. 

  77. # Client-side

  78. <client>

  79. <server>

  80. ftp

  81. </server>

  82. <killserver>

  83. ftp

  84. </killserver>

  85.  <name>

  86. FTP download with strict timeout and slow data transfer

  87.  </name>

  88.  <command timeout="1">

  89. ftp://%HOSTIP:%FTPPORT/1086 -m 7

  90. </command>

  91. </client>

  92. 

  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. PWD

  103. EPSV

  104. TYPE I

  105. SIZE 1086

  106. RETR 1086

  107. </protocol>

  108. </verify>

  109. </testcase>