> him that the directory was empty, even though the 450 response does not
> appear to be part of the RFC standards for FTP. (Unless I'm mistaken.)

You're mistaken. As per RFC959:


Section 4.2.1, the 450 response code indicates:

450 Requested file action not taken. File unavailable (e.g., file busy).

Section 5.4 explicitly indicates that the 450 response code is legal for
both the LIST and NLST commands:

125, 150
226, 250
425, 426, 451
500, 501, 502, 421, 530

125, 150
226, 250
425, 426, 451
500, 501, 502, 421, 530

Neither RFC959, nor any other FTP-related RFC, mandates which response
codes are to be used for which specific conditions for directory listings;
that is intentionally left to the server implementors.


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

There is a pleasure in the pathless woods,
There is a rapture on the lonely shore,
There is society, where none intrudes,
By the deep sea and music in its roar:
I love not man the less, but Nature more,
From these our interviews, in which I steal
From all I may be, or have been before,
To mingle with the Universe, and feel
What I can ne'er express, yet cannot all conceal.

-Lord Byron

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

This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
ProFTPD Users List
Unsubscribe problems?