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. --- CHANGES | 11 +++++++++++ 1 file changed, 11 insertions(+) (limited to 'CHANGES') diff --git a/CHANGES b/CHANGES index ada056a70..7f59f6b09 100644 --- a/CHANGES +++ b/CHANGES @@ -6,6 +6,17 @@ Changelog +Daniel Stenberg (5 Apr 2008) +- 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. + Daniel Fandrich (3 Apr 2008) - Added test627 to test SFTP with CURLOPT_NOBODY -- cgit v1.2.3