Commit 06438294 authored by Yang Tse's avatar Yang Tse
Browse files

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.
parent 75256706

tests/data/Makefile.am

+1 −1
Original line number Diff line number Diff line
@@ -64,7 +64,7 @@ EXTRA_DIST = test1 test108 test117 test127 test20 test27 test34 test46 \ 
 test1097 test560 test561 test1098 test1099 test562 test563 test1100       \

 test564 test1101 test1102 test1103 test1104 test299 test310 test311       \

 test312 test1105 test565 test800 test1106 test801 test566 test802 test803 \

 test1107 test1108 test1109 test1110 test1111

 test1107 test1108 test1109 test1110 test1111 test1112



filecheck:

	@mkdir test-place; \

tests/data/test1112

0 → 100644
+88 −0
Original line number Diff line number Diff line 
<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.

</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">

-k --ftp-ssl-control ftps://%HOSTIP:%FTPSPORT/1112 -m 3

</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>