<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> # The protocol part does not include QUIT simply because the error is # CURLE_OPERATION_TIMEDOUT (28) which is a generic timeout error without # specifically 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. <protocol> USER anonymous PASS ftp@example.com PWD EPRT |1| TYPE I SIZE 1209 RETR 1209 </protocol> <errorcode> 28 </errorcode> </verify> </testcase>