mirror of
https://github.com/moparisthebest/curl
synced 2024-11-17 15:05:02 -05:00
18371aaff9
researching it, it turned out he got a 550 response back from a SIZE command and then I fell over the text in RFC3659 that says: The presence of the 550 error response to a SIZE command MUST NOT be taken by the client as an indication that the file cannot be transferred in the current MODE and TYPE. In other words: the change I did on September 30th 2008 and that has been included in the last two releases were a regression and a bad idea. We MUST NOT take a 550 response from SIZE as a hint that the file doesn't exist.
53 lines
678 B
Plaintext
53 lines
678 B
Plaintext
<testcase>
|
|
<info>
|
|
<keywords>
|
|
FTP
|
|
PASV
|
|
RETR
|
|
multi
|
|
</keywords>
|
|
</info>
|
|
|
|
# Server-side
|
|
<reply>
|
|
<data>
|
|
</data>
|
|
|
|
<servercmd>
|
|
REPLY RETR 550 the file doesn't exist
|
|
REPLY SIZE 550 Can't check for file existence
|
|
</servercmd>
|
|
</reply>
|
|
|
|
# Client-side
|
|
<client>
|
|
<server>
|
|
ftp
|
|
</server>
|
|
<tool>
|
|
lib533
|
|
</tool>
|
|
<name>
|
|
FTP RETR twice using multi: non-existing host and non-existing file
|
|
</name>
|
|
<command>
|
|
ftp://non-existing-host.haxx.se/path/534 ftp://%HOSTIP:%FTPPORT/path/534
|
|
</command>
|
|
</client>
|
|
|
|
# Verify data after the test has been "shot"
|
|
<verify>
|
|
<protocol>
|
|
USER anonymous
|
|
PASS ftp@example.com
|
|
PWD
|
|
CWD path
|
|
EPSV
|
|
TYPE I
|
|
SIZE 534
|
|
RETR 534
|
|
QUIT
|
|
</protocol>
|
|
</verify>
|
|
</testcase>
|