HTTP status code and its definition parsing AJAX capture callback error reference _ajax related

HTTP status Code and its definition parsing AJAX capture callback error reference

The status line contains the HTTP version, status code, and a brief description of the status code. In most cases, all answer headers except content-type are optional. However, Content-type is required, which describes the MIME type of the subsequent document. Although most answers contain a single document, there are some that are not included, such as a response to a head request that never comes with a document. There are many status codes that are actually used to identify a failed request that does not contain a document (or contains only a brief error message description).

When a user tries to access content on a server that is running Internet information Services (IIS) over HTTP, IIS returns a numeric code that represents the state of the request. The status code can indicate whether a specific request has been successful, and can also reveal the exact cause of the request failure.

1XX-Information Tips

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-part content.

3xx-redirect

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.

302-Object has been moved.
304-not modified.
307-Temporary redirection.

4xx-Client Error

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:
401.1-Logon failed.
401.2-The server configuration caused the login to fail.
401.3-Authorization is not granted because the ACL restricts resources.
401.4-Filter authorization failed. The
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 private to IIS 6.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.
403.4-Requires SSL.
403.5-Requires SSL 128. The
403.6-ip address was rejected.
403.7-Client certificates are required.
403.8-site access was denied.
403.9-Too many users.
403.10-the configuration is invalid.
403.11-Password change.
403.12-access to the mapping table is denied.
403.13-The client certificate was revoked.
403.14-Deny directory list.
403.15-The Client Access License is 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 private to IIS 6.0.
403.19-CGI cannot be performed for clients in this application pool. This error code is private to IIS 6.0.
403.20-passport Login failed. This error code is private to IIS 6.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-The HTTP predicate used to access this page is not allowed (squaremethod is not allowed)
406-The client browser does not accept the MIME type of the requested page.
407-proxy authentication is required.
412-Prerequisite failed.
413? The request entity is too large.
414-The request URI is too long.
415? media type not supported.
416? The requested scope is not satisfied.
417? Execution failed.
423? Locked error.

5XX-Server Error

The server was unable to complete the request due to an error encountered.

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? The UNC authorization credentials are incorrect. This error code is private to IIS 6.0.
500.18? The URL authorization store cannot be opened. This error code is private to IIS 6.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.
503-The service is not available. This error code is private to IIS 6.0.
504-Gateway Timeout.
505-http version is not supported.

Common HTTP status Codes and why

200-success. This status code indicates that IIS has successfully processed the request.
304-not modified. The client-requested document 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, rather than downloading the document from the server.
401.1-Login failed. The logon attempt was unsuccessful, possibly because the user name or password is invalid.
401.3-Authorization is not granted due to ACL restrictions on resources. This indicates that there is an NTFS permission problem. This error can occur even if you have the appropriate permissions for the file you are trying to access.
403.1-execution access is prohibited.

The following are two common causes of this error message:

You do not have sufficient permission to execute. For example, this error message appears if the directory where the ASP page you are attempting to access is set to none, or if you are trying to execute a CGI script that has permission to allow script only. To modify execution permissions, right-click the directory in Microsoft Management Console (MMC), and then click the Properties and Directories tab to ensure that the appropriate execution permissions are set for the content you are trying to access.

You did not set the script mapping of the file type you are trying to perform to identify the predicate you are using (for example, get or POST). To verify this, right-click the table of contents in MMC, click Properties, right-click the table of Contents tab, and configure, and then verify that the script mappings for the appropriate file type are 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.

403.3-Write access is forbidden. Verify that the IIS permissions and NTFS permissions are set to grant write access to the directory.

403.4-require SSL. Disable the Require Secure channel option or use HTTPS instead of HTTP to access the page.

403.5-Require 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 was rejected. You have configured your server to deny access to your current IP address.

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

403.8-site access is denied. You have set a domain name limit for the domain that you use to access the server.

403.9-Excessive number of users. The number of users connected to this server exceeds the connection limit you have set.

Note: Microsoft Windows Professional and Microsoft Windows XP Professional automatically set the limit of up to 10 connections on IIS. You cannot change this limit.

403.12-access to the mapping table is denied. The page you are trying to access requires a client certificate, but the user ID that is mapped to your client certificate has been denied access to the file.

404-not found. This error occurs because the file you are trying to access has been moved or deleted. This error can also occur if you attempt to access a file with a limited extension after you install the URLScan tool. In this case, the word "Rejected by URLScan" appears in the log file entry for the request.

500-Internal server error. Many server-side errors can cause this error message. The Event Viewer log contains more detailed reason for the error. In addition, you can disable friendly HTTP error messages to receive detailed error descriptions.

500.12-the application is rebooting. This means that you are attempting to load an ASP page while IIS restarts the application. This information disappears when the page is refreshed. If the page is refreshed, this information appears again, possibly because antivirus software is scanning the Global.asa file.

500-100.asp-asp error. This error message appears if an ASP page that you are trying to load contains an error code. To get a more accurate error message, disable the friendly HTTP error message. By default, this error message is enabled only on the default Web site.

502-Gateway error. This error message appears if the CGI script you are trying to run does not return a valid set of HTTP headers.