moparisthebest/curl
1
0
Fork 0
mirror of https://github.com/moparisthebest/curl synced 2025-03-11 07:39:50 -04:00
Code Issues Releases Wiki Activity

- Based on the Debian bug report #474224 that complained about the FTP error

Browse Source 
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.
This commit is contained in:
Daniel Stenberg 2008-04-05 21:02:38 +00:00
parent 12a90289ed
commit 7607d5145b
2 changed files with 13 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
CHANGES
View File

@ -6,6 +6,17 @@
Changelog 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) Daniel Fandrich (3 Apr 2008)
- Added test627 to test SFTP with CURLOPT_NOBODY - Added test627 to test SFTP with CURLOPT_NOBODY

3
lib/ftp.c
View File

@ -2563,7 +2563,8 @@ static CURLcode ftp_statemach_act(struct connectdata *conn)
switch(ftpc->state) { switch(ftpc->state) {
case FTP_WAIT220: case FTP_WAIT220:
if(ftpcode != 220) { 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; return CURLE_FTP_WEIRD_SERVER_REPLY;
} }