summaryrefslogtreecommitdiff
path: root/tests/data/test546
diff options
context:
space:
mode:
authorDaniel Stenberg <daniel@haxx.se>2008-12-08 20:20:51 +0000
committerDaniel Stenberg <daniel@haxx.se>2008-12-08 20:20:51 +0000
commit18371aaff999d4862a32d060f03d8f668e8fa1b1 (patch)
tree3f2ea6ffedbcb1f43e26f418078ad18ced2db6e0 /tests/data/test546
parentf36eab2608f473a7054f2c75c411abd676657a70 (diff)
downloadgnurl-18371aaff999d4862a32d060f03d8f668e8fa1b1.tar.gz
gnurl-18371aaff999d4862a32d060f03d8f668e8fa1b1.tar.bz2
gnurl-18371aaff999d4862a32d060f03d8f668e8fa1b1.zip
- Fred Machado posted about a weird FTP problem on the curl-users list and when
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.
Diffstat (limited to 'tests/data/test546')
-rw-r--r--tests/data/test5463
1 files changed, 3 insertions, 0 deletions
diff --git a/tests/data/test546 b/tests/data/test546
index 415848792..1dd1cd41e 100644
--- a/tests/data/test546
+++ b/tests/data/test546
@@ -19,6 +19,8 @@ works
</data>
<servercmd>
+REPLY RETR 550 the file doesn't exist
+COUNT RETR 1
REPLY SIZE 550 Can't check for file existence
COUNT SIZE 1
</servercmd>
@@ -50,6 +52,7 @@ CWD path
EPSV
TYPE I
SIZE 546
+RETR 546
EPSV
SIZE 546
RETR 546