Unity-Technologies
/
curl
зеркало из https://github.com/Unity-Technologies/curl.git
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность
curl/tests/data/test1086

111 строки
4.3 KiB
Plaintext
Исходник Обычный вид История

Added test 1086 to test a timeout the occurs during an FTP data transfer.
2008-11-06 03:13:18 +03:00
<testcase>
<info>
<keywords>
FTP
EPSV
RETR
timeout
FAILURE
Added the "flaky" keyword to a number of tests Each shows evidence of flakiness on at least one platform on the autobuilds. Users can use this keyword to skip these tests if desired.
2014-10-26 15:48:46 +03:00
flaky
Added test 1086 to test a timeout the occurs during an FTP data transfer.
2008-11-06 03:13:18 +03:00
</keywords>
</info>
# Server-side
<reply>
Shortened some FTP responses to allow the timeout to be reduced by a second while still causing a timeout during the data phase.
2008-11-13 04:45:59 +03:00
# Overload some standard FTP responses to make them shorter and faster
# to avoid wasting time waiting for the data phase to start
Added test 1086 to test a timeout the occurs during an FTP data transfer.
2008-11-06 03:13:18 +03:00
<servercmd>
SLOWDOWN
Shortened some FTP responses to allow the timeout to be reduced by a second while still causing a timeout during the data phase.
2008-11-13 04:45:59 +03:00
REPLY USER 331 OK
REPLY PASS 230 OK
REPLY PWD 257 "/"
REPLY TYPE 200 OK
Added test 1086 to test a timeout the occurs during an FTP data transfer.
2008-11-06 03:13:18 +03:00
</servercmd>
<data nocheck="yes">
Long chunk of data that couldn't possibly be sent in the time allotted.
Long chunk of data that couldn't possibly be sent in the time allotted.
Long chunk of data that couldn't possibly be sent in the time allotted.
Long chunk of data that couldn't possibly be sent in the time allotted.
Long chunk of data that couldn't possibly be sent in the time allotted.
Long chunk of data that couldn't possibly be sent in the time allotted.
Long chunk of data that couldn't possibly be sent in the time allotted.
Long chunk of data that couldn't possibly be sent in the time allotted.
Long chunk of data that couldn't possibly be sent in the time allotted.
Long chunk of data that couldn't possibly be sent in the time allotted.
Long chunk of data that couldn't possibly be sent in the time allotted.
Long chunk of data that couldn't possibly be sent in the time allotted.
Long chunk of data that couldn't possibly be sent in the time allotted.
Long chunk of data that couldn't possibly be sent in the time allotted.
Long chunk of data that couldn't possibly be sent in the time allotted.
Long chunk of data that couldn't possibly be sent in the time allotted.
Long chunk of data that couldn't possibly be sent in the time allotted.
Long chunk of data that couldn't possibly be sent in the time allotted.
Long chunk of data that couldn't possibly be sent in the time allotted.
Long chunk of data that couldn't possibly be sent in the time allotted.
Long chunk of data that couldn't possibly be sent in the time allotted.
Long chunk of data that couldn't possibly be sent in the time allotted.
Long chunk of data that couldn't possibly be sent in the time allotted.
Long chunk of data that couldn't possibly be sent in the time allotted.
added an additional second to allow test to pass on heavily loaded servers
2010-02-04 12:55:45 +03:00
Long chunk of data that couldn't possibly be sent in the time allotted.
Long chunk of data that couldn't possibly be sent in the time allotted.
Long chunk of data that couldn't possibly be sent in the time allotted.
Long chunk of data that couldn't possibly be sent in the time allotted.
Long chunk of data that couldn't possibly be sent in the time allotted.
Long chunk of data that couldn't possibly be sent in the time allotted.
Long chunk of data that couldn't possibly be sent in the time allotted.
Long chunk of data that couldn't possibly be sent in the time allotted.
Long chunk of data that couldn't possibly be sent in the time allotted.
Long chunk of data that couldn't possibly be sent in the time allotted.
Long chunk of data that couldn't possibly be sent in the time allotted.
Long chunk of data that couldn't possibly be sent in the time allotted.
Long chunk of data that couldn't possibly be sent in the time allotted.
Long chunk of data that couldn't possibly be sent in the time allotted.
Long chunk of data that couldn't possibly be sent in the time allotted.
Long chunk of data that couldn't possibly be sent in the time allotted.
Long chunk of data that couldn't possibly be sent in the time allotted.
Long chunk of data that couldn't possibly be sent in the time allotted.
Long chunk of data that couldn't possibly be sent in the time allotted.
Long chunk of data that couldn't possibly be sent in the time allotted.
Long chunk of data that couldn't possibly be sent in the time allotted.
Long chunk of data that couldn't possibly be sent in the time allotted.
Long chunk of data that couldn't possibly be sent in the time allotted.
Long chunk of data that couldn't possibly be sent in the time allotted.
Long chunk of data that couldn't possibly be sent in the time allotted.
Long chunk of data that couldn't possibly be sent in the time allotted.
Added test 1086 to test a timeout the occurs during an FTP data transfer.
2008-11-06 03:13:18 +03:00
</data>
</reply>
# Client-side
<client>
<server>
ftp
</server>
<killserver>
ftp
</killserver>
<name>
FTP download with strict timeout and slow data transfer
</name>
<command timeout="1">
added an additional second to allow test to pass on heavily loaded servers
2010-02-04 12:55:45 +03:00
ftp://%HOSTIP:%FTPPORT/1086 -m 7
Added test 1086 to test a timeout the occurs during an FTP data transfer.
2008-11-06 03:13:18 +03:00
</command>
</client>
# Verify data after the test has been "shot"
<verify>
# 28 is CURLE_OPERATION_TIMEDOUT
<errorcode>
28
</errorcode>
<protocol>
USER anonymous
PASS ftp@example.com
PWD
EPSV
TYPE I
SIZE 1086
RETR 1086
</protocol>
</verify>
</testcase>