Web Status Code

These status codes represent a temporary response. The client should be prepared to receive one or more 1xx responses before receiving a regular response.
100-Continue.
101-Switch protocol.
2XX-Success

This type of status code indicates that the server successfully accepted the client request.
200-OK. The client request was successful.
201-created.
202-accepted.
203-Non-authoritative information.
204-no content.
205-Reset the content.
206-Partial content.
207-Multi-state (WebDAV).
3xx-redirect

The client browser must take more action to implement the request. For example, the browser might have to request a different page on the server, or repeat the request through a proxy server.
301-Moved Permanently
302-The object has been moved.
304-not modified.
307-Temporary redirection.
4xx-Client Error

An error occurred and the client appears to be having problems. For example, a client requests a page that does not exist, and the client does not provide valid authentication information.
400-Bad request.
401-access is denied. IIS defines several 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:
401.1-Login failed.
401.2-The server configuration caused the login to fail.
401.3-not authorized due to ACL restrictions on resources.
401.4-Filter Authorization failed.
401.5-ISAPI/CGI application authorization failed.
401.7– is denied access by the URL validation policy on the WEB server. This error code is specific to IIS 6.0.
403-Forbidden: IIS defines several different 403 errors that indicate a more specific cause of the error:
403.1-execution access is forbidden.
403.2-Read access is forbidden.
403.3-Write access is forbidden.
403.4-Requires SSL.
403.5-Requires SSL 128.
The 403.6-IP address is rejected.
403.7-Requires a client certificate.
403.8-site access is denied.
403.9-Excessive number of users.
403.10-Invalid configuration.
403.11-Password change.
403.12-Deny access to the mapping table.
403.13-The client certificate is revoked.
403.14-Reject 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 is not yet valid.
403.18-The requested URL cannot be executed in the current application pool. This error code is specific to IIS 6.0.
403.19-CGI cannot be executed for clients in this application pool. This error code is specific to IIS 6.0.
403.20-passport Login failed. This error code is specific to IIS 6.0.
404-not found.
404.0-(None) – No files or directories found.
404.1-The Web site cannot be accessed through the requested port.
The 404.2-web service extension lockout policy blocks this request.
This request was blocked by the 404.3-mime mapping policy.
405-The HTTP verb used to access this page is not allowed (method not allowed)
406-The client browser does not accept the MIME type of the requested page.
407-proxy authentication is required.
412-Precondition failed.
413– request entity is too large.
414-The request URI is too long.
415– media types not supported.
The 416– cannot satisfy the requested range.
417– execution failed.
423– a locked error.
5XX-Server Error

The server could not complete the request because it encountered an error.
500-Internal server error.
500.12-The 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.
500.16–unc authorization credentials are incorrect. This error code is specific to IIS 6.0.
500.18– cannot open the URL authorization repository. This error code is specific to IIS 6.0.
500.19-The data for this file is not configured correctly in the metabase.
500.100-Internal ASP error.
501-The header value specifies the 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.
502.2-CGI Application error.
503-The service is not available. This error code is specific to IIS 6.0.
504-The gateway timed out.
505-http version is not supported.
IIS HTTP status codes and their causes
200-success. This status code indicates that the request was successfully processed by IIS.
206-Partial content. This indicates that a file has been partially downloaded. You can continue to upload corrupted downloads, or split the download into multiple concurrent streams.
207-Multi-state (WebDAV). There should be an XML message before this message, which might contain several separate response codes, depending on how many sub-requests were made.
301-has been permanently moved. Both this request and all subsequent requests should go to the specified URI.
302-found. For forms-based authentication, this message is typically expressed as "object moved." The requested resource temporarily resides in a different URI. Because redirects can sometimes change, clients should continue to use Request-uri in future requests. This response can be cached only if indicated in the Cache-control or Expires header field.
304-not modified. The document requested by the client is already in its cache and the document has not been modified since it was cached. The client uses a cached copy of the document instead of downloading the file from the server.
401.1 and 401.2-Login failed. The logon attempt failed because the user name or password is invalid or there is a problem with the system configuration. For more information about how to resolve this issue, click the following article number to view the article in the Microsoft Knowledge Base:
907273 (http://support.microsoft.com/kb/907273/) to exclude HTTP 401 errors in IIS
401.3-not authorized due to ACL restrictions on resources. This indicates that there is an NTFS permission issue. This error can occur even if you have the appropriate permissions for the file you are trying to access. For example, if the IUSR account does not have permission to access the C:\Winnt\System32\Inetsrv directory, you will see this error. For more information about how to resolve this issue, click the following article number to view the article in the Microsoft Knowledge Base:
271071 (http://support.microsoft.com/kb/271071/) How to set the required NTFS permissions and user rights for the IIS 5.0 WEB server
812614 (http://support.microsoft.com/kb/812614/) default permissions and user rights for IIS 6.0
403-Forbidden: If the site does not have a default document set and is not set to allow directory browsing, you will receive this generic 403 status code. For more information about how to resolve this issue, click the following article number to view the article in the Microsoft Knowledge Base:
320051 (http://support.microsoft.com/kb/320051/) How to configure default documents in Internet information Services
403.1-execution access is forbidden. The following are the two common causes of this error message:
You do not have sufficient permission to execute. For example, this error message occurs if you try to access an ASP page that has the directory permission set to None, or if you try to execute a CGI script that has the directory permission of "script only allowed." To modify execution permissions, right-click the directory in the Microsoft Management Console (MMC), click the properties and then the Directory tab, and then make sure that the appropriate execution permissions are set for the content you are trying to access.
You have not set the script mapping of the file type you are trying to execute to recognize the verb (for example, GET or POST) that you are using. To verify this, right-click the table of contents in the Microsoft Management console, click Properties, clicking the Directory tab, and then verify that the script map for the appropriate file type is set to allow the verbs that are used.
403.2-Read access is forbidden. Verify that IIS is set to allow read access to the directory. Also, if you are using the default file, verify that the file exists. For additional information about how to resolve this issue, click the article number below to view the article in the Microsoft Knowledge Base:
247677 (http://support.microsoft.com/kb/247677/) error message: 403.2 forbidden:read access Forbidden (403.2 Forbidden: Read access Forbidden)
403.3-Write access is forbidden. Verify that IIS permissions and NTFS permissions are set to grant write access to the directory. For additional information about how to resolve this issue, click the article number below to view the article in the Microsoft Knowledge Base:
248072 (http://support.microsoft.com/kb/248072/) error message: 403.3 forbidden:write access Forbidden (403.3 Forbidden: Write access Forbidden)
403.4-Requires SSL. Disable the Require secure channel option, or use HTTPS instead of HTTP to access the page. If the error does not appear on the Web site where the certificate is installed, click the following article number to view the article in the Microsoft Knowledge Base:
224389 (http://support.microsoft.com/kb/224389/) error message in Internet information Server 4.0: "HTTP Error 403, 403.4, 403.5 Fo Rbidden:ssl Required "(HTTP error 403, 403.4, 403.5 Forbidden: SSL required)
403.5-Requires SSL 128. Disable the Require 128-bit encryption option, or use a browser that supports 128-bit encryption to view the page.
The 403.6-IP address is rejected. You have configured the server to deny access to your current IP address. For additional information about how to resolve this issue, click the article number below to view the article in the Microsoft Knowledge Base:
248043 (http://support.microsoft.com/kb/248043/) error message: 403.6-forbidden:ip address rejected (403.6-unavailable: IP address denied)
403.7-Requires a client certificate. You have configured the server to require a certificate for client authentication, but you do not have a valid client certificate installed.
186812 (http://support.microsoft.com/kb/186812/) PRB: Error message: 403.7 forbidden:client Certificate Required (403.7 Forbidden: Require client certificate)
403.8-site access is denied. You have set a domain name limit for the domain used to access the server. For additional information about how to resolve this issue, click the article number below to view the article in the Microsoft Knowledge Base:
248032 (http://support.microsoft.com/kb/248032/) error message: Forbidden:site access Denied 403.8 (Forbidden: Site denied access 403.8)
403.9-Excessive number of users. The number of users connected to the server exceeds the connection limit that you set. For additional information about how to change this limit, click the following article number to view the article in the Microsoft Knowledge Base:
248074 (http://support.microsoft.com/kb/248074/) error message: Access forbidden:too many Users are Connected 403.9 (Access Forbidden: Too many users connected 403.9)
Note Microsoft Windows Professional and Windows XP Professional automatically set a limit of up to 10 connections on IIS. You cannot change this limit.
403.12-Deny access to the mapping table. The page you want to access requires a client certificate. However, the user ID that is mapped to the client certificate has been denied access to the file. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
248075 (http://support.microsoft.com/kb/248075/) Error: http 403.12-access forbidden:mapper Denied Access (http 403.12-Forbidden Stop access: Mapper denied access)
404-not found. This error occurs because the file that you are trying to access has been moved or deleted. This error can also occur if you try to access a file with a limited extension after you install the URLScan tool. If you installed the Uriscan tool, you will see "Rejected by URLScan" in the w3svc log file. In this case, the word "Rejected by URLScan" appears in the log file entry for the request. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
248033 (http://support.microsoft.com/kb/248033/) IIS server returned "HTTP 404-file not Found" (HTTP 404-File not found) common causes of errors
404.1– cannot access the Web site through the requested port. This error message indicates that the IP address of the Web site you are trying to access does not accept requests from the port used for this request. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
248034 (http://support.microsoft.com/kb/248034/) IIS error: 404.1 Web site not Found (404.1 found)
This request was blocked by the 404.2– lock policy. In IIS 6.0, this indicates that the request has been blocked in the list of Web service extensions. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
328419 (http://support.microsoft.com/kb/328419/) How to add and remove Web service extension files in IIS 6.0
328505 (http://support.microsoft.com/kb/328505/) How to List Web service extensions and extension files in IIS 6.0
328360 (http://support.microsoft.com/kb/328360/) How to enable and disable ISAPI extensions and CGI applications in IIS 6.0
This request was blocked by the 404.3-mime mapping policy. This problem occurs if the following conditions exist:
The handler mappings for the requested file name extensions are not configured.
No corresponding MIME type is configured for the Web site or application.
405– methods are not allowed. This error occurs when the client sends an HTTP request to the server that is running IIS, and the request contains an HTTP verb that is not recognized by the server. To resolve this issue, make sure that the client's request uses HTTP verbs that are compatible with HTTP RFC. For information about the HTTP RFC, see the "References" section.
500-Internal server error. Many server-side errors can cause this error message. The Event Viewer log contains a more detailed cause of the error. Additionally, you can disable the friendly HTTP error message in order to receive a detailed error description. For more information about how to display friendly HTTP error messages, click the following article number to view the article in the Microsoft Knowledge Base:
294807 (http://support.microsoft.com/kb/294807/) How to:disable Internet Explorer 5 ' Show friendly http Error Messages ' Feature on the Server Side
500.12-the application is restarting. This indicates that you attempted to load an ASP page during IIS restart of the application. When the page is refreshed, the message disappears. If this message appears again after the page is refreshed, the antivirus software may be scanning the Global.asa file. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
248013 (http://support.microsoft.com/kb/248013/) error message: HTTP error 500-12 Application restarting (HTTP errors 500-12 application is restarting Move
500-100.asp-asp error. This error message appears if you try to load an ASP page that contains an error code. To get a more precise error message, disable the friendly HTTP error message. By default, this error message is only enabled on the default Web site. For additional information about how to see this error message on a non-default Web site, click the following article number to view the article in the Microsoft Knowledge Base:
261200 (http://support.microsoft.com/kb/261200/) displays an HTTP 500 error message without displaying an ASP error message for 500-100.asp
502-Gateway error. This error message occurs if the CGI script that you are trying to run does not return a valid set of HTTP headers. To resolve this issue, you must debug the CGI application to determine why it is passing invalid HTTP information to IIS.
The 503– service is not available. Starting with IIS 6, the kernel-mode HTTP. SYS component generates an HTTPS 503 state. For more information about how to determine and troubleshoot HTTP 503 errors, click the following article number to view the article in the Microsoft Knowledge Base:
820729 (http://support.microsoft.com/kb/820729/) error logging in the HTTP API
500.19. You receive this error if the XML metabase contains invalid configuration information in the content type that you are trying to access. To resolve this issue, remove or correct the invalid configuration. This problem usually indicates that there is a problem in the ScriptMap metabase key.
Ftp
1XX-Affirmative Initial reply

These status codes indicate that an operation has started successfully, but the client wants to get another reply before continuing with the new command.
110 Restart Tag reply.
120 service is ready, starting in nnn minutes.
125 The data connection is open and the transfer is starting.
150 file status OK, ready to open data connection.
2XX-sure to complete the reply

An operation has been successfully completed. The client can execute the new command.
200 command OK.
202 commands are not executed and there are too many commands on the site.
211 System Status, or system help reply.
212 Directory status.
213 file status.
214 Help message.
215 Name System type, where name is the formal system name listed in the Assigned Numbers document.
220 The service is ready to execute the request of the new user.
221 Service closes the control connection. If appropriate, please log out.
225 Data connection Open, no in-progress transfer.
226 Close the data connection. The requested file operation was successful (for example, transferring a file or discarding a file).
227 Enter 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 "PATHNAME" has been created.
3xx-Affirmative Intermediate reply

The command was successful, but the server needs more information from the client to complete the processing of the request.
331 user name is correct, password required.
332 You need to log in to your account.
350 The requested file operation is waiting for further information.
4xx-Complete reply for transient negation

The command is unsuccessful, but the error is temporary. If the client retries the command, it may execute successfully.
421 service is not available and the control connection is shutting down. If the service determines that it must be closed, this response is sent to any command.
425 The data connection cannot be opened.
426 Connection closed; Transfer aborted.
450 The requested file operation was not performed. The file is not available (for example, the file is busy).
451 requested operation aborted: Local error is being processed.
452 the requested operation was not performed. The system does not have enough storage space.
5XX-Permanent negation of complete reply

The command is unsuccessful and the error is permanent. If the client retries the command, the same error will occur again.
500 syntax error, command not recognized. This may include errors such as the command line being too long.
501 There are syntax errors in the arguments.
502 command not executed.
503 wrong sequence of commands.
504 command not executed for this parameter.
530 not logged in.
532 The account is required to store the file.
550 the requested operation was not performed. The file is not available (for example, the file was not found and no access was granted).
551 requested operation aborted: unknown page type.
552 requested file operation terminated abnormally: storage allocation exceeded (for current directory or dataset).
553 The requested operation was not performed. The file name is not allowed.
Common FTP status codes and their causes
The 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 is closed.
230-The status code is displayed after the client sends the correct password. It indicates that the user has successfully logged on.
331-The status code is displayed after the client sends the user name. The status code is displayed regardless of whether the provided user name is a valid account in the system.
426-The command opens the data connection to perform the operation, but the operation has been canceled and the data connection is closed.
530-The status code indicates that the user cannot log on because the user name and password combination is not valid. If you are logged on with a user account, you might 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 try to put the file into a directory where you do not have write permission.
Back to the top

Web Status Code