<testcase> <info> <keywords> FTP RETR huge response </keywords> </info> # Server-side <reply> <data> mooo </data> # A long set of response strings to CWD to make sure the ftp parser deals # with it nicely. The length hits a boundary condition that may make curl # hang. <servercmd> REPLY CWD 250-AAAAAAAAAAAAAAAAAAAAAAAAA\r\n%repeat[218 x 250-AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA\r\n]%250 Finally, here is the response </servercmd> </reply> # Client-side <client> <server> ftp </server> <name> FTP with large number of command response lines (boundary condition) </name> <command> ftp://%HOSTIP:%FTPPORT/path/%TESTNUMBER </command> </client> # Verify data after the test has been "shot" <verify> <protocol crlf="yes"> USER anonymous PASS [email protected] PWD CWD path EPSV TYPE I SIZE %TESTNUMBER RETR %TESTNUMBER QUIT </protocol> </verify> </testcase>
