HTTP Status codes and Definitions (interpretation) _ Basics

Most recently, the state of Ajax requests, or the state of a server-side Cross-domain request, is now a collection of the following articles.

When we normally browse the Web, we also find that some files do not exist and appear as "404 Errors", which is the common HTTP request status (status)

When a Web server responds to a request from a browser or other client, its answer typically consists of a status line, several answer headers, a blank line, and a content document. Here is one of the simplest answers:

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 the initial request has been accepted and the customer should continue to send the remainder of the request. (HTTP 1.1 new)
· 101-switching Protocols server converts customer requests to another protocol (HTTP 1.1 new)

2XX-Success

This type of status code indicates that the server successfully accepted the client request.
· 200-ok everything is fine, the answer document for Get and post requests follows.
· The 201-created server has created the document, and the location header gives its URL.
· 202-accepted has accepted the request, but processing has not yet completed.
· The 203-non-authoritative information document has returned normally, but some answer headers may be incorrect because a copy of the document is being used, not authoritative information (HTTP 1.1 new).
· 204-no Content does not have a new document, the browser should continue to display the original document. This status code is useful if the user periodically refreshes the page and the servlet can determine that the user's document is new enough.
· 205-reset content has no new contents, but the browser should reset what it displays. Used to force the browser to clear form input (HTTP 1.1 new).
· 206-partial Content customer sent a GET request with a range header, and the server completed it (HTTP 1.1 new).

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.
· 300-multiple choices Client-requested documents can be found in multiple locations, which are already listed in the returned document. If the server wants to make a preference, it should be indicated in the location answer header.
· 301-moved permanently client-requested documents elsewhere, the new URL is given in the location header, and the browser should automatically access the new URL.
· 302-found is similar to 301, but the new URL should be treated as a temporary alternative, not permanent. Note that the corresponding state information in the HTTP1.0 is "moved temporatily". When this status code appears, the browser can automatically access the new URL, so it is a useful status code. Note that this status code can sometimes be replaced with 301. For example, if the browser incorrectly requests Http://host/~user (a trailing slash is missing), some servers return 301, and some return 302. Strictly speaking, we can only assume that the browser will automatically redirect only if the original request is get. Please see 307.
· 303-see is similar to 301/302, except that if the original request was a post,location header specified redirect target document should be extracted via get (HTTP 1.1 new).
· 304-not Modified The client has a buffered document and makes a conditional request (typically providing a if-modified-since header that indicates that the customer wants to update only a document that is newer than the specified date). The server tells the customer that the previously buffered document can continue to be used.
· 305-use Proxy Client-requested documents should be extracted via the proxy server indicated by the location header (HTTP 1.1 new).
· 307-temporary Redirect and 302 (Found) are the same. Many browsers incorrectly respond to 302 responses for redirection, even if the original request is post, even if it is actually only redirected when the POST request is answered at 303. For this reason, HTTP 1.1 has been added 307 to further clear the locale code: when a 303 reply occurs, the browser can follow the redirected get and post requests, and if 307 answers, the browser can only follow the redirection of the got request. (HTTP 1.1 new)

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.

· A syntax error occurred in the 400-bad request.

· 401-unauthorized access was denied and the customer attempted to access a password-protected page without authorization. A www-authenticate header is included in the answer, the browser displays the user name/password dialog Accordingly, and then makes the request again after filling in the appropriate authorization header. 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-Login failed.
· 401.2-The 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 private to IIS 6.0.

· 403-forbidden resource is not available. The server understands the customer's request, but refuses to process it. This is usually caused by a permission setting on a file or directory on the server. 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 forbidden.
· 403.3-Write access is forbidden.
· 403.4-Require SSL.
· 403.5-Requires SSL 128.
· 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.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-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 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 cannot find a resource at the specified location. This is also a common answer.
· 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.

· The 405-method not allowed request method (GET, POST, head, Delete, put, Trace, and so on) does not apply to the specified resource, and HTTP predicates used to access this page are not allowed (methods are not allowed) (HTTP 1.1 new)
· 406-not acceptable The specified resource has been found, but its MIME type is incompatible with the client specified in the Accpet header, and the client browser does not accept the MIME type of the requested page (HTTP 1.1 new).
· 407-proxy authentication Required requires proxy authentication, similar to 401, which means that the customer must first be authorized by the proxy server. (HTTP 1.1 new)
· 408-request Timeout The customer has not made any requests for the duration of the server's license. Customers can repeat the same request at a later time. (HTTP 1.1 new)
· 409-conflict are usually associated with put requests. The request cannot succeed because the request and the current state of the resource are conflicting. (HTTP 1.1 new)
· 410-gone the requested document is no longer available and the server does not know which address should be redirected to. It differs from 404 in that the return of 407 indicates that the document left the specified location permanently, while 404 indicates that the document is not available because of an unknown reason. (HTTP 1.1 new)
· 411-length Required server cannot process requests unless the client sends a content-length header. (HTTP 1.1 new)
· Some prerequisites specified in the 412-precondition Failed request header failed (HTTP 1.1 new).
· 413–request Entity Too Large the size of the target document exceeds the size that the server is currently willing to handle. If the server considers itself able to process the request later, it should provide a Retry-after header (HTTP 1.1 new).
· 414-request URI Too Long URI (HTTP 1.1 new).
· 415– media type that is not supported.
· The 416–requested range not satisfiable server does not meet the range header specified by the customer in the request. (HTTP 1.1 new)
· 417– execution failed.
· 423– the locked error.

5XX-Server Error

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

· The 500-internal server Error servers encountered unexpected conditions and could not complete the customer's request.

· 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.
· The 500.16–unc authorization credentials are incorrect. This error code is private to IIS 6.0.
· The 500.18–url authorization store cannot be opened. This error code is private to IIS 6.0.
· 500.100-Internal ASP error.

· The 501-not implemented server does not support the functionality required to implement the request, and the header value specifies the not implemented configuration. For example, the customer issued a put request that the server does not support.

· The 502-bad gateway server, as a gateway or proxy, accesses the next server in order to complete the request, but the server returns an illegal reply. It is also said that the Web server received an invalid response when it was used as a gateway or proxy server.

· The 502.1-cgi application timed out.
· Error 502.2-cgi application.

· The 503-service unavailable service is unavailable and the server fails to respond due to maintenance or overload. For example, a servlet might return 503 if the database connection pool is full. The server can provide a retry-after header when it returns 503. This error code is private to IIS 6.0.

· 504-gateway Timeout Network Guan Shu is used by a server acting as a proxy or gateway, indicating that the answer cannot be received from the remote server in a timely manner. (HTTP 1.1 new).

· The 505-http version not supported server does not support HTTP versions as specified in the request. (HTTP 1.1 new).