From 7607d5145bbacd76d45bca405edc12f4b613418c Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Sat, 5 Apr 2008 21:02:38 +0000 Subject: - Based on the Debian bug report #474224 that complained about the FTP error message when libcurl doesn't get a 220 back immediately on connect, I now changed it to be more specific on what the problem is. Also worth noticing: while the bug report contains an example where the response is: 421 There are too many connected users, please try again later we cannot assume that the error message will always be this readable nor that it fits within a particular boundary etc. --- lib/ftp.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'lib') diff --git a/lib/ftp.c b/lib/ftp.c index 061189c98..769bc8b14 100644 --- a/lib/ftp.c +++ b/lib/ftp.c @@ -2563,7 +2563,8 @@ static CURLcode ftp_statemach_act(struct connectdata *conn) switch(ftpc->state) { case FTP_WAIT220: if(ftpcode != 220) { - failf(data, "This doesn't seem like a nice ftp-server response"); + failf(data, "Got a %03d ftp-server response when 220 was expected", + ftpcode); return CURLE_FTP_WEIRD_SERVER_REPLY; } -- cgit v1.2.3