Opened 7 years ago

Closed 3 years ago

Last modified 3 years ago

#8731 closed Feature request (rejected)

LIST or NLST commands behavior\reply if file not exists — at Version 4

Reported by: Vlad Owned by:
Priority: normal Component: FileZilla Server
Keywords: Cc:
Component version: Operating system type: Windows
Operating system version: Server 2008 R2 64

Description (last modified by Tim Kosse)

Most FTP servers do not return an error for commands

LIST file.ext

or

NLST file.ext

if the file not exists.
Reply of FileZilla server is:

200 Port command successful
550 Directory not found

Reply of SERV-U FTP server for example is:

200 PORT Command successful.
150 Opening ASCII mode data connection for /bin/ls.
226 Transfer complete.

Is there a possibility to change the server's response and did not return an error?
If you can not make changes to the future version, can you to recommend changes of code to implement this behavior?

Thank you

Change History (4)

comment:1 by Kurt McKee, 4 years ago

Triage suggestion

It appears the user is requesting that FileZilla Server stop reporting errors when files do not exist.

I suggest closing this ticket.

comment:2 by Kurt McKee, 4 years ago

Resolution: rejected
Status: newclosed

comment:3 by cdmaslo, 3 years ago

Priority: highnormal
Resolution: rejected
Status: closedreopened

It looks like the original request was correct. This behaviour is not compliant with RFC 959.
For consistency, this command should return the successful completion codes and no data files, as follows:

ftp> ls abc
200 PORT command successful.
150 Opening data connection for abc.
226 Transfer complete.

For example, there was a similar error in FTPD server and IBM fixed it (http://www-01.ibm.com/support/docview.wss?uid=isg1IV36935)

comment:4 by Tim Kosse, 3 years ago

Description: modified (diff)
Resolution: rejected
Status: reopenedclosed

From RFC 959:

NAME LIST (NLST)

            This command causes a directory listing to be sent from
            server to user site.  The pathname should specify a
            directory or other system-specific file group descriptor;

As such the error is correct, as the pathname does not specify a directory and (by virtue of not having them at all) neither a system-specific file group descriptor.

Technically NLST on an ordinary file isn't implemented correctly in FileZilla Server, that command too should fail but doesn't as an ordinary file is not a directory.

Last edited 3 years ago by Tim Kosse (previous) (diff)
Note: See TracTickets for help on using tickets.