Developer on Alibaba Coud: Build your first app with APIs, SDKs, and tutorials on the Alibaba Cloud. Read more ＞
When a user attempts to access content on a server that is running Internet Information Services (IIS) through HTTP or File Transfer Protocol (FTP), IIS returns a numeric code that represents the state of the request. The status code is recorded in the IIS log and may also be displayed in a Web browser or FTP client. The status code can indicate whether a specific request has been successful, and can also reveal the exact cause of the request failure.
Location of log files
In the default state, IIS places its log files in the%windir\system32\logfiles folder. Each World Wide Web (WWW) site and FTP site have a separate directory under that directory. By default, log files are created in these directories on a daily basis, and the log files are named with dates (for example, ExYYMMDD.log).
These status codes represent a temporary response. The client should be prepared to receive one or more 1xx responses before receiving a regular response.
This type of status code indicates that the server successfully accepted the client request.
200-OK. The client request was successful.
205-Reset the content.
The client browser must take more action to implement the request. For example, a browser might have to request a different page on the server, or repeat the request through a proxy server.
301-The object has been permanently removed, that is, permanent redirection.
302-The object has been temporarily moved.
An error occurred and the client appears to have a problem. For example, a client requests a page that does not exist, and the client does not provide valid authentication information. 400-the wrong request.
401-access is denied. IIS defines a number of different 401 errors that indicate a more specific cause of the error. These specific error codes are displayed in the browser but are not displayed in the IIS log:
The 401.2-server configuration caused the login to fail.
401.3-Authorization is not granted due to ACL restrictions on resources.
401.4-Filter Authorization failed.
401.5-ISAPI/CGI application authorization failed.
401.7– access is denied by the URL authorization policy on the Web server. This error code is dedicated to IIS6.0.
403-Prohibit access: IIS defines a number of different 403 errors that indicate a more specific cause of the error:
403.1-execution access is prohibited.
403.2-Read access is prohibited.
403.3-Write access is prohibited.
The 403.6-IP address was rejected.
403.7-Client certificate required.
403.8-site access is denied.
403.9-Excessive number of users.
403.10-Configuration is not valid.
403.12-access to the mapping table is denied.
403.13-The client certificate was revoked.
403.14-Deny directory list.
403.15-Client access permission exceeded.
403.16-Client certificate is not trusted or invalid.
403.17-The client certificate has expired or has not yet taken effect.
403.18-The requested URL cannot be executed in the current application pool. This error code is dedicated to IIS6.0.
403.19-CGI cannot be performed for clients in this application pool. This error code is dedicated to IIS6.0.
403.20-passport Login failed. This error code is dedicated to IIS6.0.
404-not found. 404.0-(None) – No files or directories found.
404.1-The Web site cannot be accessed on the requested port.
The 404.2-web service extension lockout policy blocks this request.
The 404.3-mime mapping policy blocks this request.
405-HTTP predicates used to access this page are not allowed (methods are not allowed)
406-The client browser does not accept the MIME type of the requested page.
407-proxy authentication is required.
The 413– request entity is too large.
414-The request URI is too long.
415– media type that is not supported.
416– the requested range is not satisfied.
417– execution failed.
423– the locked error.
The server was unable to complete the request due to an error encountered.
500-Internal server error.
The 500.12-application is busy restarting on the Web server.
The 500.13-web server is too busy.
500.15-Direct Request Global.asa is not allowed.
The 500.16–unc authorization credentials are incorrect. This error code is dedicated to IIS6.0.
The 500.18–url authorization store cannot be opened. This error code is dedicated to IIS6.0.
500.100-Internal ASP error.
501-The header value specifies a configuration that is not implemented.
An invalid response was received when the 502-web server was used as a gateway or proxy server.
The 502.1-cgi application timed out.
Error 502.2-cgi application. Application.
503-The service is not available. This error code is dedicated to IIS6.0.
The 504-gateway timed out.
505-http version is not supported.
1xx-a positive initial reply
These status codes indicate that an operation has started successfully, but the client expects another reply before continuing with the new command.
110 reboot the tag reply.
120 The service is ready and starts after nnn minutes.
125 The data connection is turned on and the transfer is starting.
150 file status is normal, ready to open data connection.
2xx-definitely complete the answer
An operation has completed successfully. The client can execute the new command. 200 the command determines.
202 command is not executed, too many commands on the site.
211 System State, or system help reply.
212 Directory status.
213 file status.
214 Help messages.
215NAME system type, where name is the official system name listed in the Assignednumbers document.
220 The service is ready to execute the new user's request.
221 The service closes the control connection. If appropriate, please log off.
225 The data connection is open and no transmission is in progress.
226 Close the data connection. The requested file operation was successful (for example, transferring a file or discarding a file).
227 into the passive mode (H1,H2,H3,H4,P1,P2).
230 The user is logged in and continues.
250 The requested file operation is correct and completed.
257 has created "PATHNAME".
3xx-Affirmation of the middle reply
The command was successful, but the server needed more information from the client to complete processing of the request. 331 username is correct and requires a password.
332 login account required.
350 The requested file operation is waiting for further information.
Complete response to 4xx-transient negation
The command did not succeed, but the error is temporary. If the client retries the command, it may execute successfully. The 421 service is not available and is shutting down the control connection. If the service determines that it must be closed, this response is sent to any command.
425 The data connection could not be opened.
450 The requested file operation was not executed. File is not available (for example, the file is busy).
451 the requested operation terminated abnormally: A local error is being processed.
452 the requested operation was not performed. The system does not have enough storage space.
5xx-a permanent negative completion reply
The command is not successful and the error is permanent. If the client retries the command, the same error occurs again. 500 syntax error, command not recognized. This may include errors such as the command line being too long.
501 There is a syntax error in the parameter.
502 did not execute the command.
503 wrong sequence of commands.
504 The command that did not execute the parameter.
530 not logged in.
532 requires an account for storing files.
550 the requested operation was not performed. File is not available (for example, file not found, no access rights).
551 The requested operation terminated abnormally: Unknown page type.
552 requested file operation terminated abnormally: Excess storage allocation (for current directory or dataset).
553 The requested operation was not performed. The file name that is not allowed.
Common FTP status Codes and why
150-FTP uses two ports: 21 for sending commands and 20 for sending data. Status code 150 indicates that the server is ready to open a new connection on port 20 and send some data.
226-The command opens a data connection on port 20 to perform operations, such as transferring files. The operation completed successfully and the data connection was closed.
230-After the client sends the correct password, the status code is displayed. It indicates that the user has successfully logged in.
331-The status code is displayed after the client sends the user name. The status code is displayed regardless of whether the user name provided is a valid account on the system.
426-The command opens the data connection to perform the operation, but the operation has been canceled and the data connection has been closed.
530-The status code indicates that the user cannot log on because the user name and password combination are invalid. If you are logged on with a user account, you may type an incorrect user name or password, or you may choose to allow only anonymous access. If you log on with an anonymous account, the configuration of IIS may deny anonymous access.
550-The command was not executed because the specified file is not available. For example, the file you want to get does not exist, or you are trying to put the file to a directory where you do not have write permission.
This article is an English version of an article which is originally in the Chinese language on aliyun.com and is provided for information purposes only. This website makes no representation or warranty of any kind, either expressed or implied, as to the accuracy, completeness ownership or
reliability of the article or any translations thereof. If you have any concerns or complaints relating to the article, please send an email, providing a detailed description of the concern or
complaint, to firstname.lastname@example.org. A staff member will contact you within 5 working days. Once verified, infringing content will be removed immediately.
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
and provide relevant evidence. A staff member will contact you within 5 working days.