|Subject:||Re: FTP problem in both Indy 9 and 10|
|Posted by:||Remy Lebeau (Indy Team) (firstname.lastname@example.org)|
|Date:||Mon, 31 Jul 2006|
"news.wi.rr.com" <aols…@bizwi.rr.com> wrote in message
> Why is this?
There is no way to answer that without more details. What does the actual
drectory listing data look like? Use a packet sniffer to find out. Chances
are the items are not able to be parsed properly. FTP listings are very
difficult to parse because they are not sent in any kind of standardized
format, so servers are free to send anything they wish.
There are some Drafts that define new MLSD and MLST commands for
standardizing the listing format for easier parsing. Indy 9 does not
support those new commands, but Indy 10 does. You have to set the UseMLIS
property to True to enable them (it is False by default). Even then, the
server has to support the commands in order for TIdFTP to issue them.
Otherwise, it falls back to the old NLST and LIST commands, which have no
standard format, so parsing has a lot of guess-work in it and can
occasionally fail to operate properly. Also, don't forget to include the
desired IdFTPListParse... units into your 'uses' clause if you plan on using
the DirectoryListing property, or else it will not be able to parse the item
data into the collection.
FTP problem in both Indy 9 and 10 posted by news.wi.rr.com on Mon, 31 Jul 2006