On Tue, Jun 2, 2009 at 8:51 AM, Niklas Gustavsson <nik...@protocol7.com> wrote:
> On Tue, Jun 2, 2009 at 3:31 AM, Sai Pullabhotla
> <sai.pullabho...@jmethods.com> wrote:
>> I would like to say that the results you have indicated only come from FTP
>> servers that actually run the UNIX's ls command when a NLST command is
>> received. Other servers probably adhere to the RFC by just returning names.
>
> One addition to this list, FileZilla works as described by Dennis.
Another one, proftpd prints full path, but does not support parent
directories (".." seems to be ignored). Does support home directory
paths, but translated them to absolute paths (from the root of the
file system).
All of this seems to be a mess, not sure that we conclude that we do
the wrong, nor the right thing at the moment. At least clients can not
assume anything and thus probably have to find the file names (without
the path) in whatever gets returned. Of course, the client knows the
path already, since it sent it.
Dennis, could you maybe describe some further on why you need to full
path and how your client interoperates with servers that do not full
support this (like proftpd which is a major player in this area).
/niklas
