> Unfortunately, the patch in bugzilla 2863 does not solve the issue.
> It's the 450 answer that confuses the client, which it takes as a
> problem with obtaining the directory listing and thus refuses to
> continue. proftpd 1.2 used to deliver an empty listing with a 226
> return code, which is what the client expects.


RFC959 does not dictate a particular behavior to which FTP server
implementations must conform when handling the LIST command on nonexistent
files. Therefore ProFTPD's current behavior is not necessarily a bug; in
this case your client needs to handle both cases. In fact, I would argue
that sending an 4xx error response code is better than a 2xx response
code, indicating success of some sort.

TJ

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

He that complies against his will
Is of his own opinion still.

-Samuel Butler

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?p...rge&CID=DEVDEV
_______________________________________________
ProFTPD Users List
Unsubscribe problems?
http://www.proftpd.org/list-unsub.html