Use the REPLY226 statement to direct the FTP server to reply to the FTP client with reply code 226 instead of reply code 250 to command sequences described in RFC 959; these command sequences enable the server to choose between reply code 226 and reply code 250.
Tips:
- FTP reply codes are described in RFC 959.
- Generally, reply code 226 or 250 is used after a successful file transfer, after LIST commands, and after NLST commands.
- Reply code 250 (but not 226) is used for a broader class of FTP commands, such as RNTO, DELE, MKD, RMD, CWD.
- RFC 959 describes the command sequences where a server is allowed to reply with either reply code 226 or reply code 250.
Syntax
.-REPLY226 FALSE------. >>-+---------------------+------------------------------------->< '-REPLY226--+-FALSE-+-' '-TRUE--'
Parameters
- FALSE
- Directs the server to reply to the client with code 250 after successful file transfer, and after other FTP commands that enable the server to choose between reply code 250 and reply code 226. This is the default.
- TRUE
- Directs the server to reply to the client with reply code 226 instead of reply code 250 after successful file transfer, and after other FTP commands that enable the server to choose between reply code 250 and reply code 226.
Restriction: A server is not always permitted to select reply 226 instead of reply 250. The REPLY226 setting does not override RFC 959 in these cases. For example, RFC 959 stipulates the server must reply with reply code 250 to RMD (remove directory); the REPLY226 setting does not affect the reply code selected for RMD commands.
Examples
To direct the client to reply
with code 226 instead of code 250 for successful file transfer, and
for other command sequences described in RFC 959 that enable the server
to choose between reply code 226 and reply code 250, enter the following
code in the server's FTP.DATA:
REPLY226 TRUE