Newsgroups : Borland : borland.public.delphi.internet.winsock : 2007 Feb : Re: Indy FTP Response Codes for NLST
| Subject: | Re: Indy FTP Response Codes for NLST |
| Posted by: | "Remy Lebeau (TeamB)" (no.spam@no.spam.com) |
| Date: | Wed, 14 Feb 2007 03:05:49 |
"Erik Berry" <eb@techie.ZZZcom> wrote in message
news:45d2db61$1@newsgroups.borland.com...
> My FTP server returns a response 226 with a text of "Transfer
Complete."
Then your server is very buggy. 226 must not be the first response
code that is sent in reply to the NLST command. It must send 125 or
150 first. 125 and 150 establish the presence of a valid data channel
connection, and then 26 indicates the success of the transfer over
that connection. RFC 959 is very clear on this matter.
> Because the code 226 is not in the array of acceptable responses
above,
> it raises an exception from TIdReplyRFC.RaiseReplyError eventually.
As it should be, because the server is not following the established
standard in the first place.
Gambit