232, 234, 250, 253, 257 FTP Response Codes

A 232 code may be sent in response to a USER command if the server is willing to allow the user access based on previously exchanged security data.

Example response

232 User logged in, authorized by security data exchange.

Possible command:

• USER

A 234 code is sent in response to the AUTH command when the requested security mechanism is accepted and negotiation of the secured connection can begin.

Example response

234 AUTH command OK. Initializing SSL connection.

Possible command:

• AUTH

A 250 code is sent in response to the successful completion of a file related command or user working directory related command.

Example response

250 Requested file action okay, completed.

Possible commands:

• APPE
• CDUP
• CWD
• DELE
• LIST
• MLSD
• MLST
• NLST
• RETR
• RMD
• RMDA
• RNTO
• SMNT
• STOU
• STOR
• XCRC

The 253 code is sent in response to the successful completion of a change to a file’s attributes or date/time.

Example response

253 Date/time changed okay.

253 Attributes changed okay.

Possible commands:

• MLSD
• SITE CHMOD

A 257 code is used as a successful response to the creation of a new directory from the MKD command or in response to a PWD command.

Example response

257 “PATHNAME” created.

Possible commands:

• MKD
• PWD

• 110, 120, 125, 150 FTP response codes
• 202, 211, 212, 213 FTP response codes
• 214, 215, 220, 221 FTP response codes
• 225, 226, 227, 230 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