HTTP TFP status explanation

When a user tries through HTTP or File Transfer Protocol  access to a running Internet Information Services (IIS) of (FTP) server when content on, IIS returns a numeric code that represents the status of the request. The status code is recorded in the IIS log, and may also appear in the Web browser or FTP client. Specific status code can indicate whether the request has been successful, but also reveal the exact reason for the failure of the request

HTTP

1xx - Information Tips

These status codes indicate a provisional response. Before a client receiving a regular response, should be prepared to receive one or more 1xx response. · 100-- continue.

· 101-- switching protocol.

2xx - Success

Such status codes indicate that the server successfully accepted the client request. · 200-- OK. The client request has succeeded.

· 201-- has been created.

· 202-- has been accepted.

· 203 - Non-authoritative information.

· 204-- empty.

· 205-- Reset content.

· 206-- part.

3xx - Redirection

The client browser must take more action to fulfill the request. For example, the browser may have to request a different page on the server, or through a proxy server repeat the request. · 302-- object has moved.

· 304-- unmodified.

· 307-- temporary redirect.

4xx - Client Error

Error occurs, the client seems to have problems. For example, a client requests a page that does not exist, the client may not provide valid authentication information. · 400 - Bad request.

· 401-- access denied. IIS defines a number of different 401 errors that indicate a more specific cause of the error. These specific error codes displayed in the browser, but not in the IIS log: - 401.1 - Logon failed.

* 401.2 -  server configuration Logon failed.

* 401.3 - due to ACL on resource without authorization.

* 401.4 - Authorization failed.

· 401.5 - ISAPI / CGI application authorization failure.

* 401.7 - Access Web  server refused URL authorization policy on. This error code is  IIS 6.0  dedicated to.

· 403 - Forbidden: IIS defines a number of different 403 errors that indicate a more specific cause of the error: - 403.1 - Execute access forbidden.

* 403.2 - Read access forbidden.

* 403.3 - Write access forbidden.

* 403.4 - requires SSL.

* 403.5 - requires SSL 128.

· 403.6 - IP address rejected.

* 403.7 - Client certificate required.

* 403.8 - Site access denied.

* 403.9 - Too many users.

* 403.10 - configuration is invalid.

* 403.11 - password change.

* 403.12 - Access Denied Map.

* 403.13 - Client certificate revoked.

* 403.14 - Directory Listing Denied.

* 403.15 - Client Access Licenses.

* 403.16 - Client certificate is untrusted or invalid.

* 403.17 - Client certificate has expired or is not yet valid.

* 403.18 - in the current application pool can not perform the requested URL. This error code is specific to IIS 6.0.

* 403.19 - Can not execute CGI for the client in this application pool side. This error code is specific to IIS 6.0.

· 403.20 - Passport logon failed. This error code is specific to IIS 6.0.

· 404 - not found. * 404.0 - (None) - File or directory not found.

* 404.1 - not at the requested port accessible on the Web site.

· 404.2 - Web service extension lockdown policy prevents this request.

· 404.3 - MIME map policy prevents this request.

· 405-- used to access this page HTTP verb is not allowed (method not allowed.)

· 406-- client browser does not accept the MIME type of the requested page.

· 407 - proxy authentication .

· 412-- Precondition failed.

· 413-- Request Entity Too Large.

· 414-- request URI is too long.

· 415 - Unsupported media type.

· 416-- the scope of the request can not be met.

· 417-- failed.

· 423-- locked error.

5xx -  Server Error

Since the server encountered an error and could not complete the request. · 500 - Internal server error. * 500.12 - Application is busy restarting on the Web server.

· 500.13 - Web server is too busy.

* 500.15 - does not allow direct request for  the Global.asa .

· 500.16 - UNC authorization credentials incorrect. This error code is specific to IIS 6.0.

· 500.18 - URL authorization store can not be opened. This error code is specific to IIS 6.0.

· 500.100 - Internal ASP error.

· 501--  Header values specify a configuration that is not implemented.

· 502 - Web  server as a gateway received an invalid response or proxy server. · 502.1 - CGI application timeout.

· 502.2 - CGI  application error . application.

· 503 - Service unavailable. This error code is specific to IIS 6.0.

· 504-- Gateway timeout.

· 505 - HTTP version not supported.

Common HTTP status codes and their causes

· 200-- success. This status code represents the IIS has successfully processed the request.

· 304-- unmodified. The client requests a document is already in its cache , the cache since the document has not been modified. The client uses the cached copy of the document, rather than from the server to download the document.

* 401.1 - Logon failed. Login attempt is unsuccessful, probably because of a user name or password is invalid.

* 401.3 - due to ACL on resource without authorization. This means that the problem with NTFS permissions. Even if you have the appropriate permissions are trying to access files, this error may also occur. For example, if the IUSR account does not have access to C: \ Winnt \ System32 \ Inetsrv directory, you will see this error.

* 403.1 - Execute access forbidden. The following are two common causes leading to this error message: • You do not have enough Execute permissions. For example, if the directory permissions are trying to access the ASP page is set to "no", or an attempt to execute CGI scripts directory permissions where is "only allows script", the error message will appear. To modify the Execute permissions, Management Console (MMC) Right-click the directory in Microsoft, and then click Properties and the Directory tab, make sure to set the appropriate permissions to execute trying to access the content.

· You will not attempt to execute the script file types mapped to verb (for example, GET or POST) used to identify. To verify this, right-click the directory in the MMC, click Properties, click the Directory tab and configure, and then verify that the appropriate file type script mapping is set up to allow the use of the verb.

* 403.2 - Read access forbidden. Verify that IIS is set to allow read access to the directory. In addition, if you are using the default file, verify that the file exists.

* 403.3 - Write access forbidden. Verify that the IIS permissions and NTFS permissions are set up in order to grant write access to the directory.

* 403.4 - requires SSL. Disable the Require secure channel option, or use HTTPS instead of HTTP to access the page.

* 403.5 - requires SSL 128. Disable the Require 128-bit encryption option, or use 128-bit encryption browser to view the page.

· 403.6 - IP address rejected. You have just your server is configured to deny access to your current IP address.

* 403.7 - Client certificate required. You have just your server is configured to require client authentication certificate, but you do not have a valid client certificate installed.

* 403.8 - Site access denied. You have to use to access your server domain set up domain name restrictions.

* 403.9 - Too many users. Connected to the server, the number of users exceeds the connection limit that you set.

Note: Microsoft Windows 2000 PRofessional and Microsoft Windows XP PRofessional automatically set a limit on IIS up to 10 connections. You can not change this limit.

* 403.12 - Access Denied Map. The page you want to access requires a client certificate, but mapped to your client certificate user ID has been denied access to the file.

· 404 - not found. This error occurs because you try to access the file has been moved or deleted. If after installing URLScan tool, trying to access files with a limited extension, this error will occur. In this case, the word "Rejected by URLScan" in the log file entry of the request appear.

· 500 - Internal server error. Many server side error may result in the error message. Event Viewer log contains more detailed error reasons. In addition, you can disable friendly HTTP error messages to receive a detailed description of the error.

* 500.12 - Application is restarting. This means that you restart the application process in IIS tries to load the ASP page. After refreshing the page, this message will disappear. If you refresh the page, this message appears again, it may be anti-virus software is scanning the Global.asa file.

· 500-100.ASP - ASP error. If you try to load an ASP page that contains the error code , this error message will appear. To get a more exact error message, disable friendly HTTP error messages. By default, this error message will only be enabled on the default Web site.

· 502--  Gateway error. If you try to run a CGI script that does not return a valid set of HTTP headers, this error message will appear.