这篇文章摘自http://www.altools.net/,版权为别人所有,工作中因需要查阅,所以转载自此.
FTP response codes are 3 digits, with the first
2 digits giving specific information on the type of response, and the
final digit revealing the exact nature of the code.
Code |
Summary |
1yz |
Positive Preliminary reply
The requested action is being initiated; expect another reply
before proceeding with a new command. (The user-process sending
another command before the completion reply would be in violation
of protocol; but server-FTP processes should queue any commands
that arrive while a preceding command is in progress.) This type
of reply can be used to indicate that the command was accepted and
the user-process may now pay attention to the data connections,
for implementations where simultaneous monitoring is difficult.
The server-FTP process may send at most, one 1yz reply per command. |
2yz |
Positive Completion reply
The requested action has been successfully completed. A new request
may be initiated.
|
3yz |
Positive Intermediate reply
The command has been accepted, but the requested action is being
held in abeyance, pending receipt of further information. The user
should send another command specifying this information. This reply
is used in command sequence groups. |
4yz |
Transient Negative Completion reply
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. The user should return to the beginning
of the command sequence, if any. It is difficult to assign a meaning
to "transient", particularly when two distinct sites (Server-
and User-processes) have to agree on the interpretation. Each reply
in the 4yz category might have a slightly different time value,
but the intent is that the user-process is encouraged to try again.
A rule of thumb in determining if a reply fits into the 4yz or the
5yz (Permanent Negative) category is that replies are 4yz if the
commands can be repeated without any change in command form or in
properties of the User or Server (e.g., the command is spelled the
same with the same arguments used; the user does not change his
file access or user name; the server does not put up a new implementation.)
|
5yz |
Permanent Negative Completion reply
The command was not accepted and the requested action did not
take place. The User-process is discouraged from repeating the exact
request (in the same sequence). Even some "permanent"
error conditions can be corrected, so the human user may want to
direct his User-process to reinitiate the command sequence by direct
action at some point in the future (e.g., after the spelling has
been changed, or the user has altered his directory status.)
|
|
Code |
Summary |
x0z |
Syntax - These replies refer to syntax
errors, syntactically correct commands that don't fit any functional
category, unimplemented or superfluous commands. |
x1z |
Information - These are replies to
requests for information, such as status or help. |
x2z |
Connections - Replies referring to
the control and data connections. |
x3z |
Authentication and accounting - Replies
for the login process and accounting procedures. |
x4z |
Unspecified as yet. |
x5z |
File system - These replies indicate
the status of the Server file system vis-a-vis the requested transfer
or other file system action. |
|
Code |
Summary |
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 okay; about to open data connection. |
200 |
Command okay. |
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.
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). |
230 |
User logged in, proceed. |
250 |
Requested file action okay, completed. |
257 |
"PATHNAME" created. |
331 |
User name okay, need password. |
332 |
Need account for login. |
350 |
Requested file action pending further information. |
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.
File unavailable (e.g., file busy). |
451 |
Requested action aborted: local error in processing. |
452 |
Requested action not taken.
Insufficient storage space in system. |
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.
File name not allowed. |
* NOTE: FTP is defined in RFC
959. If you need more information on FTP response codes or FTP in general,
RFC 959
is authoritative. |