summaryrefslogtreecommitdiff
path: root/tests/data/test118
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/test118
parentf36eab2608f473a7054f2c75c411abd676657a70 (diff)
downloadcurl-18371aaff999d4862a32d060f03d8f668e8fa1b1.tar.gz
- 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/test118')
-rw-r--r--tests/data/test1183
1 files changed, 0 insertions, 3 deletions
diff --git a/tests/data/test118 b/tests/data/test118
index b2b10c235..6cd086ca2 100644
--- a/tests/data/test118
+++ b/tests/data/test118
@@ -9,9 +9,6 @@ FAILURE
</info>
# Server-side
<reply>
-<size>
-1
-</size>
<servercmd>
REPLY RETR 314 bluah you f00l!
REPLY EPSV 314 bluah you f00l!