HTTP |
100 |
Continue Continue |
101 |
Switching protocols Switch Protocol |
200 |
OK Normal |
201 |
Created Created |
202 |
Accepted Accepted |
203 |
Non-authoritative information Non-authoritative information |
204 |
NO content NO content |
205 |
Reset content Reset content |
206 |
Partial content Partial content |
300 |
Multiple Choices Multiple options |
301 |
Moved permanently Permanent redirection |
302 |
Found Temporary redirection |
303 |
See other See other |
304 |
Not modified Not modified |
305 |
Use proxy Use proxy |
307 |
Temporary redirect Temporary redirection |
400 |
Bad request Syntax Error in the request |
401 |
Unauthorized Not verified |
403 |
Forbidden Resource unavailable |
404 |
Not found The specified resource cannot be found. |
405 |
Method not allowed The request method is not allowed. |
406 |
Not acceptable Unacceptable |
407 |
Proxy authentication required Proxy verification required |
408 |
Request timeout Request timeout |
409 |
Conflict Conflict |
410 |
Gone No longer available |
411 |
Length required Length required |
412 |
Precondition failed Prerequisite failed |
413 |
Request Entity too large The Request Entity is too large. |
414 |
Request URI Too long URI The request URI is too long. |
416 |
Requested range not satisfiable The requested range cannot meet |
500 |
Internal Server Error Internal Server Error |
501 |
Not Implemented The server does not support the functions required to implement the request. |
502 |
Bad Gateway When the Web server is used as a gateway or proxy server, it receives an invalid response. |
503 |
Service unavailable Service unavailable |
504 |
Gateway timeout Gateway timeout |
505 |
HTTP Version Not Supported The HTTP version is not supported. |
FTP |
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 "= "). Restart flag response. In this case, the information is accurate and does not need to be specially processed. You can see that in the mark yyyy = Mmm, YYYY is the user process data stream mark, mmmm is the corresponding mark on the server (note the space between the mark and equal sign ). |
120 |
Service ready in NNN minutes. Service available in NNN time |
125 |
Data connection already open; transfer starting. The data connection is enabled and data transmission starts. |
150 |
File status okay; about to open data connection. The file status is correct. The data connection is being opened. |
200 |
Command okay. Command Execution ends normally. |
202 |
Command not implemented, superfluous at this site. The command is not executed. This site does not support this command. |
211 |
System status, or system help reply. System status or system help information response. |
212 |
Directory status. Directory status information. |
213 |
File status. File status information. |
214 |
Help message. on how to use the server or the meaning of a special non-standard command. This reply is useful only to the human user. Help information. About how to use this server or special non-standard commands. This reply is only useful to people. |
215 |
Name system type. Where name is an official system name from the list in the assigned numbers document. Name system type. |
220 |
Service ready for new user. The service of the newly connected user is ready. |
221 |
Service closing control connection. The control connection is closed. |
225 |
Data connection open; no transfer in progress. The data connection is enabled, and no data is being transferred. |
226 |
Closing data connection. Requested file action successful (for example, file transfer or file abort ). Closing data connection. The request file action ends successfully (for example, file transfer or termination ). |
227 |
Entering passive mode (H1, H2, H3, H4, P1, P2 ). Enter passive mode. |
230 |
User logged in, proceed. logged out if appropriate. The user has logged in. You can log out without any need. |
250 |
Requested file action okay, completed. The requested file operation is completed successfully. |
257 |
"Pathname" created. The path has been created. |
331 |
User name Okay, need password. The user name already exists. Enter the password. |
332 |
Need account for login. The account to log on. |
350 |
Requested file action pending further information More information is required for operations on the requested file. |
421 |
Service not available, closing control connection. This may be a reply Any command if the service knows it must shut down. The service is unavailable and the control connection is closed. This may be a response to any command, if the service thinks it must be disabled. |
425 |
Can't open data connection. An error occurred while enabling the data connection. |
426 |
Connection closed; Transfer aborted. The connection is closed and the transfer is aborted. |
450 |
Requested file action not taken. Operations on the requested file are not performed. |
451 |
Requested action aborted. Local error in processing. The requested operation is aborted. A local error occurs during processing. |
452 |
Requested action not taken. Insufficient storage space in system. File unavailable (e.g., file busy ). The requested operation is not executed. Insufficient system storage space. File is unavailable. |
500 |
Syntax error, command unrecognized. This may include errors such as command line too long. Syntax error, unrecognized command. This may be because the command line is too long. |
501 |
Syntax Error in parameters or arguments. Syntax Error Caused by parameter error. |
502 |
Command not implemented. The command is not executed. |
503 |
Bad sequence of commands. Command Order error. |
504 |
Command not implemented for that parameter. The command is not executed due to a parameter error. |
530 |
Not logged in. No logon. |
SMTP |
200 |
(Nonstandard success response, see rfc876) (For non-standard success responses, see rfc876) |
211 |
System status, or system help reply System status or system help reply |
214 |
Help message Help Information |
220 |
<Domain> Service ready <Domain Name> Service ready |
221 |
<Domain> Service closing transmission channel <Domain Name> the service is disabling the transmission channel. |
250 |
Requested mail action okay, completed The requested email operation is OK. |
251 |
User not local; will forward to <forward-path> Non-local user; will go to <forward-path> |
354 |
Start mail input; end with <CRLF>. <CRLF> Start entering the email; end with <CRLF>. <CRLF> |
421 |
<Domain> service not available, closing transmission channel <Domain Name> the service is unavailable. The transmission channel is being disabled. |
450 |
Requested mail action not taken: Mailbox unavailable The requested email operation is not accepted: the email address is unavailable. |
451 |
Requested action aborted: Local error in Processing Request operation interrupted: an internal error occurred while processing |
452 |
Requested action not taken: insufficient system storage Requested operation not executed: insufficient system space |
500 |
Syntax error, command unrecognised Language error. Unknown command |
501 |
Syntax Error in parameters or arguments The syntax of the parameter or variable is incorrect. |
502 |
Command not implemented Command not implemented yet |
503 |
Bad sequence of commands Incorrect command order |
504 |
Command Parameter not implemented Command Parameter not implemented yet |
521 |
<Domain> does not accept mail (see rfc1846) <Domain Name> do not accept emails (see rfc1846) |
530 |
Access denied Access prohibited |
550 |
Requested action not taken: Mailbox unavailable Requested operation not executed: Mailbox unavailable |
551 |
User not local; please try <forward-path> Non-local user; try <forward-path> |
552 |
Requested mail action aborted: exceeded Storage Allocation The requested email operation has been interrupted: the requested email exceeds the allocated space. |
553 |
Requested action not taken: mailbox name not allowed Requested operation not executed: the email name is not allowed |
554 |
Transaction Failed Transmission failed |