moparisthebest/curl
1
0
Fork 0
mirror of https://github.com/moparisthebest/curl synced 2024-11-16 06:25:03 -05:00
Code Issues Releases Wiki Activity
7cbe4d8d79
curl/tests/data/test1112

115 lines
4.4 KiB
Plaintext
Raw Normal View History

Added test case #1112 which does an FTPS download with strict timeout and slow data transfer in a similar way as test case #1086 does for FTP. This also exercises <killserver> section for the FTPS server.
2010-01-12 17:29:18 -05:00
<testcase>
<info>
<keywords>
FTPS
EPSV
RETR
timeout
FAILURE
</keywords>
</info>
# Server-side
<reply>
# Overload some standard FTP responses to make them shorter and faster
# to avoid wasting time waiting for the data phase to start
<servercmd>
SLOWDOWN
REPLY USER 331 OK
REPLY PASS 230 OK
REPLY PWD 257 "/"
REPLY TYPE 200 OK
</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-02 20:41:07 -05: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 case #1112 which does an FTPS download with strict timeout and slow data transfer in a similar way as test case #1086 does for FTP. This also exercises <killserver> section for the FTPS server.
2010-01-12 17:29:18 -05:00
</data>
</reply>
# Client-side
<client>
<features>
SSL
</features>
<server>
ftps
</server>
<killserver>
ftps
</killserver>
<name>
FTPS download with strict timeout and slow data transfer
</name>
<command timeout="1">
test1112: Increase the timeout from 7s to 16s As someone reported on the mailing list a while back, the hard-coded arbitrary timeout of 7s in test 1112 is not sufficient in some build environments. At Arista Networks we build and test curl as part of our automated build system, and we've run into this timeout 170 times so far. Our build servers are typically quite busy building and testing a lot of code in parallel, so despite being beefy machines with 32 cores and 128GB of RAM we still hit this 7s timeout regularly. URL: http://curl.haxx.se/mail/lib-2010-02/0200.html
2013-09-21 23:27:19 -04:00
-k --ftp-ssl-control ftps://%HOSTIP:%FTPSPORT/1112 -m 16
Added test case #1112 which does an FTPS download with strict timeout and slow data transfer in a similar way as test case #1086 does for FTP. This also exercises <killserver> section for the FTPS server.
2010-01-12 17:29:18 -05: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
PBSZ 0
PROT C
PWD
EPSV
TYPE I
SIZE 1112
RETR 1112
</protocol>
</verify>
</testcase>
Reference in New Issue Copy Permalink