202, 211, 212, 213 FTP Response Codes

A 202 response is meant to indicate that the command is recognized but not implemented by the server because it has no use or meaning to the server. It is considered a successful reply because the client can continue its FTP transaction as if the command was successfully completed on the server.

Example response

202 Command not implemented, superfluous at this site.

Possible commands:

• ACCT
• ALLO
• PASS
• SITE

A 211 code is given in response to commands asking for status or help from the server. The information contained along with the response is intended for user consumption and rarely has a meaning to the client process itself.

Example response

211 System status, or system help reply.

Possible commands:

• HELP
• STAT

A 212 code is given in response to a command asking for directory status information. A STAT command that includes a path parameter is one command where a 212 response would be expected.

Example response

212 Directory status.

Possible command:

• STAT

A 213 code may be given in response to a command asking for status information on a file transfer. A STAT command issued during a file transfer is one command where a 213 response code would be expected.

Example response

213 File status.

Possible commands:

• STAT
• AVBL
• DSIZ
• MFCT
• MFMT

• 110, 120, 125, 150 FTP response codes
• 214, 215, 220, 221 FTP response codes
• 225, 226, 227, 230 FTP response codes
• 232, 234, 250, 253, 257 FTP response codes
• 331, 332, 334, 336, 350 FTP response codes
• 401, 421, 425, 426 FTP response codes
• 431, 450, 451, 452 FTP response codes
• 500, 501, 502, 503, 504 FTP response codes
• 530, 532, 533, 534, 535 FTP response codes
• 536, 550, 551, 552, 553 FTP response codes