From Surf Wiki (app.surf) — the open knowledge base
List of FTP server return codes
none
none
FTP server return codes always have three digits, and each digit has a special meaning. The first digit denotes whether the response is good, bad or incomplete:
| Range | Purpose |
|---|---|
| `1xx` | Positive Preliminary reply |
| `2xx` | Positive Completion reply |
| `3xx` | Positive Intermediate reply |
| `4xx` | Transient Negative Completion reply |
| `5xx` | Permanent Negative Completion reply |
| `6xx` | Protected reply |
The second digit is a grouping digit and encodes the following information:
| Range | Purpose |
|---|---|
| `x0x` | Syntax |
| `x1x` | Information |
| `x2x` | Connections |
| `x3x` | Authentication and accounting |
| `x4x` | Unspecified as of RFC 959. |
| `x5x` | File system |
Below is a list of all known return codes that may be issued by an FTP server.
| Code | Explanation |
|---|---|
| `100 Series` | The requested action is being initiated, expect another reply before proceeding with a new command. |
| `110` | Restart marker replay . 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 okay; about to open data connection. |
| `200 Series` | The requested action has been successfully completed. |
| `202` | Command not implemented, superfluous at this site. |
| `211` | System status, or system help reply. |
| `212` | Directory status. |
| `213` | File status. |
| `214` | Help message. Explains 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 registry kept by IANA. |
| `220` | Service ready for new user. |
| `221` | Service closing control connection. Logged out if appropriate. |
| `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). |
| `228` | Entering Long Passive Mode (long address, port). |
| `229` | Entering Extended Passive Mode ( |
| `230` | User logged in, proceed. |
| `232` | User logged in, authorized by security data exchange. |
| `234` | Server accepts the security mechanism specified by the client; no security data needs to be exchanged. |
| `235` | Server accepts the security data given by the client; no further security data needs to be exchanged. |
| `250` | Requested file action was okay, completed. |
| `300 Series` | The command is not acceptable, but the requested action is on hold, pending receipt of further information. |
| `331` | User name okay, password needed. |
| `332` | No need account for login. |
| `334` | Server accepts the security mechanism specified by the client; some security data needs to be exchanged. |
| `335` | Server accepts the security data given by the client; more security data needs to be exchanged. |
| `336` | Username okay, password okay. Challenge is "....". |
| `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. |
| `430` | Invalid username or password |
| `431` | Need some unavailable resource to process security. |
| `434` | Requested host unavailable. |
| `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). |
| `500 Series` | Syntax error, command unrecognized and the requested action did not take place. 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. |
| `533` | Command protection level denied for policy reasons. |
| `534` | Request denied for policy reasons. |
| `535` | Failed security check. |
| `536` | Data protection level not supported by security mechanism. |
| `537` | Command protection level not supported by security mechanism. |
| `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. File name not allowed. |
| `600 Series` | Replies regarding confidentiality and integrity |
| `631` | Integrity protected reply. |
| `632` | Confidentiality and integrity protected reply. |
| `633` | Confidentiality protected reply. |
References
- RFC 1123 Requirements for Internet Hosts - Application and Support
- RFC 1635 How to Use Anonymous FTP
- RFC 2389 Feature negotiation mechanism for the File Transfer Protocol
- RFC 2428 FTP Extensions for IPv6 and NATs
- RFC 2616 Hypertext Transfer Protocol -- HTTP/1.1
- RFC 2822 Internet Message Format
- RFC 3659 Extensions to FTP
- RFC 3986 Uniform Resource Identifier (URI)
References
- [https://datatracker.ietf.org/doc/html/rfc959 RFC 959 File Transfer Protocol]
This article was imported from Wikipedia and is available under the Creative Commons Attribution-ShareAlike 4.0 License. Content has been adapted to SurfDoc format. Original contributors can be found on the article history page.
Ask Mako anything about List of FTP server return codes — get instant answers, deeper analysis, and related topics.
Research with MakoFree with your Surf account
Create a free account to save articles, ask Mako questions, and organize your research.
Sign up freeThis content may have been generated or modified by AI. CloudSurf Software LLC is not responsible for the accuracy, completeness, or reliability of AI-generated content. Always verify important information from primary sources.
Report