2011-11-12 02:46:44 +08:00
|
|
|
<testcase>
|
|
|
|
<info>
|
|
|
|
<keywords>
|
|
|
|
FTP
|
|
|
|
PORT
|
|
|
|
RETR
|
|
|
|
NODATACONN
|
|
|
|
</keywords>
|
|
|
|
</info>
|
|
|
|
# Server-side
|
|
|
|
<reply>
|
|
|
|
<data nocheck="yes">
|
|
|
|
some bytes
|
|
|
|
</data>
|
|
|
|
<servercmd>
|
|
|
|
NODATACONN
|
|
|
|
</servercmd>
|
|
|
|
</reply>
|
|
|
|
|
|
|
|
# Client-side
|
|
|
|
<client>
|
|
|
|
<server>
|
|
|
|
ftp
|
|
|
|
</server>
|
|
|
|
<name>
|
|
|
|
FTP PORT download, no data conn and no positive preliminary reply
|
|
|
|
</name>
|
|
|
|
<command>
|
|
|
|
--max-time %FTPTIME2 ftp://%HOSTIP:%FTPPORT/1209 -P -
|
|
|
|
</command>
|
|
|
|
|
|
|
|
</client>
|
|
|
|
|
|
|
|
# Verify data after the test has been "shot"
|
|
|
|
<verify>
|
|
|
|
<strippart>
|
|
|
|
s/^EPRT \|1\|(.*)/EPRT \|1\|/
|
|
|
|
</strippart>
|
2011-11-26 05:38:13 +08:00
|
|
|
|
|
|
|
# The protocol part does not include QUIT simply because the error is
|
|
|
|
# CURLE_OPERATION_TIMEDOUT (28) which is a generic timeout error without
|
|
|
|
# specificly saying for which connection it concerns, and for timeouts libcurl
|
|
|
|
# marks the control channel as "invalid". As this test case times out for the
|
|
|
|
# data connection it could still use the control channel.
|
2011-11-12 02:46:44 +08:00
|
|
|
<protocol>
|
|
|
|
USER anonymous
|
|
|
|
PASS ftp@example.com
|
|
|
|
PWD
|
|
|
|
EPRT |1|
|
|
|
|
TYPE I
|
|
|
|
SIZE 1209
|
|
|
|
RETR 1209
|
|
|
|
</protocol>
|
|
|
|
<errorcode>
|
2011-11-26 05:38:13 +08:00
|
|
|
28
|
2011-11-12 02:46:44 +08:00
|
|
|
</errorcode>
|
|
|
|
</verify>
|
|
|
|
</testcase>
|