821094ba72
Also, make the ftp server return a canned response that doesn't cause XML verification problems. Although the test file format isn't technically XML, it's still handy to be able to use XML tools to verify and manipulate them.
74 lines
1.2 KiB
Plaintext
74 lines
1.2 KiB
Plaintext
<testcase>
|
|
<info>
|
|
<keywords>
|
|
FTP
|
|
RETR
|
|
</keywords>
|
|
</info>
|
|
|
|
# Server-side
|
|
<reply>
|
|
<data nocheck="yes">
|
|
fooo
|
|
mooo
|
|
</data>
|
|
</reply>
|
|
|
|
# Client-side
|
|
<client>
|
|
<server>
|
|
ftp
|
|
</server>
|
|
<name>
|
|
FTP DL, file without C-D inside, using -o fname -i -D stdout
|
|
</name>
|
|
<command option="no-output,no-include">
|
|
ftp://%HOSTIP:%FTPPORT/path/file1384 -o log/download1384 -i -D -
|
|
</command>
|
|
<postcheck>
|
|
perl %SRCDIR/libtest/notexists.pl log/file1384
|
|
</postcheck>
|
|
</client>
|
|
|
|
# Verify data after the test has been "shot"
|
|
<verify>
|
|
<protocol>
|
|
USER anonymous
|
|
PASS ftp@example.com
|
|
PWD
|
|
CWD path
|
|
EPSV
|
|
TYPE I
|
|
SIZE file1384
|
|
RETR file1384
|
|
QUIT
|
|
</protocol>
|
|
|
|
<file1 name="log/download1384">
|
|
fooo
|
|
mooo
|
|
</file1>
|
|
|
|
<file2 name="log/stdout1384">
|
|
220- _ _ ____ _
|
|
220- ___| | | | _ \| |
|
|
220- / __| | | | |_) | |
|
|
220- | (__| |_| | _ {| |___
|
|
220 \___|\___/|_| \_\_____|
|
|
331 We are happy you popped in!
|
|
230 Welcome you silly person
|
|
257 "/" is current directory
|
|
250 CWD command successful.
|
|
229 Entering Passive Mode (stripped)
|
|
200 I modify TYPE as you wanted
|
|
213 10
|
|
150 Binary data connection for 1384 () (10 bytes).
|
|
226 File transfer complete
|
|
</file2>
|
|
<stripfile2>
|
|
s/^(229 Entering Passive Mode \().*(\).*)/${1}stripped${2}/
|
|
</stripfile2>
|
|
|
|
</verify>
|
|
</testcase>
|