LIST or NLST commands behavior\reply if file not exists

[Vlad]

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

[Kurt McKee]

Triage suggestion

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

I suggest closing this ticket.

[cdmaslo]

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)

[Tim Kosse]

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.