FTP status codes

http_status_code

Bron: coffeecup.com

500 Series: The command was not accepted and the requested action did not take place.

500   Syntax error, command unrecognized. This may include errors such as command line too long.
501   Syntax error in parameters or arguments.
502   Command not implemented.
503   Bad sequence of commands.
504   Command not implemented for that parameter.
530   Not logged in.
532   Need account for storing files.
550   Requested action not taken. File unavailable (e.g. file not found, no access).
551   Requested action aborted. Page type unknown.
552   Requested file action aborted. Exceeded storage allocation (for current directory or dataset).
553   Requested action not taken. Filename not allowed.

400 Series: The command was not accepted and the requested action did not take place, but the error condition is temporary and the action may be requested again.

421   Service not available, closing control connection.This may be a reply to any command if the service knows it must shut down.
425   Can’t open data connection.
426   Connection closed; transfer aborted.
450   Requested file action not taken.
451   Requested action aborted. Local error in processing.
452   Requested action not taken. Insufficient storage space in system. File unavailable (e.g. file busy).

300 Series: The command has been accepted, but the requested action is dormant, pending receipt of further information.

331   Username OK, need password.
332   Need account for login.
350   Requested file action pending further information.

200 Series: The requested action has been successfully completed.

200   Command OK.
202   Command not implemented, superfluous at this site.
211   System status, or system help reply.
212   Directory status.
213   File status.
214   Help message on how to use the server or the meaning of a particular non-standard command. This reply is useful only to the human user.
215   NAME system type, where NAME is an official system name from the list in the Assigned Numbers document.
220   Service ready for new user.
221   Service closing control connection.
225   Data connection open; no transfer in progress.
226   Closing data connection. Requested file action successful (for example, file transfer or file abort).
227   Entering Passive mode (h1,h2,h3,h4,p1,p2).
230   User logged in, proceed. Logged out if appropriate.
250   Requested file action OK, completed.
257   “PATHNAME” created.

100 Series: The requested action is being initiated; expect another reply before proceeding with a new command.

110   Restart marker reply. In this case, the text is exact and not left to the particular implementation; it must read: MARK yyyy = mmmm where yyyy is User-process data stream marker, and mmmm server’s equivalent marker. (Note the spaces between markers and “=”.)
120   Service ready in nnn minutes.
125   Data connection already open; transfer starting.
150   File status OK; about to open data connection.

Top