HTTP response Code

HTTP response Code

1XX-Message Notification

These status codes represent a temporary response. The client receives a regular response. should be prepared to receive one or more 1xx should.

· 100-continue the initial request has been accepted, the customer should continue to send the remainder of the request.

[1.1]
· 101-switching Protocols Server translates the client's request to the second protocol.

[1.1]


2XX-Success

This type of status code indicates that the server successfully accepted the client request.

· 200-ok Everything is OK, the answer document for Get and post requests is followed.
· 201-created server has created the document, and the location header gives its URL.

· 202-accepted has accepted the request, but the processing is not complete.
· 203-non-authoritative information The document has returned normally. However, some answer headers may not be correct, because the use of a copy of the document, non-authoritative information. [1.1]
· 204-no Content does not have a new document. The browser should continue to display the original document.

Assume that the user refreshes the page periodically. The servlet can determine that the user documentation is new enough. This status code is very practical.
· 205-reset content is not new, but the browser should reset what it displays.

Used to force the browser to clear the form input.

[1.1]
· The 206-partial Content client sends a GET request with a range header, and the server finishes it.

[1.1]


3xx-redirect

The client browser must take many other actions to implement the request. For example, the browser might have to request a different page on the server, or repeat the request through Proxy server.
· 300-multiple Choices Client-requested documents can be found in multiple locations that have been listed in the returned document.

Assume that the server wants to make a priority choice. Should be indicated in the location answer header.
· 301-moved permanently The document requested by the customer elsewhere, the new URL is given in the location header, and the browser should be proactive in visiting the new URL.
· 302-found is similar to 301, but the new URL should be considered a temporary replacement. Instead of being permanent. Note that the corresponding status information in HTTP1.0 is "Moved temporatily". When the status code appears, the browser can proactively access the new URL, so it is a very useful status code.

Note that this status code can sometimes be used with 301 substitutions. For example, suppose the browser mistakenly requests Http://host/~user (the trailing slash is missing), some servers return 301, and some return 302. Strictly speaking. We can only assume that the browser will proactively redirect itself only when the original request is get. Please see 307.
· 303-see other is similar to 301/302, except that. Suppose the original request was post. The redirect target document specified by the location header should be fetched through get.

[1.1]
· The 304-not Modified client has a buffered document and issues a conditional request (usually providing a if-modified-since header indicating that the customer only wants to update the document over the specified date).

The server tells the customer that the original buffered document can continue to be used.
· 305-use Proxy The document requested by the client should be extracted from the proxy server indicated by the location header. [1.1]
· 307-temporary Redirect and 302 (Found) are the same. Many browsers incorrectly respond to a 302 response for redirection, even if the original request is post, even though it can actually only be redirected when the answer to the POST request is 303. For this reason, HTTP 1.1 has been added in 307 to clear the region in several status codes: When a 303 response occurs, the browser is able to follow the redirected get and post requests, and assuming that the 307 answer, the browser can only follow the redirect to the GET request. [1.1]


4xx-client Error

Error occurs. The client seems to have a problem. Like what. Client requests a page that does not exist, and the client does not provide valid authentication information.
· 400-bad request syntax error occurred.
· 401-unauthorized access was denied. The customer attempted to access a page protected by password without authorization. A www-authenticate header is included in the answer. The browser displays the username Word/password dialog box and then makes a request again after filling in the appropriate authorization header.

IIS defines a number of different 401 errors, which indicate a more detailed cause of the error.

These detailed error codes are displayed in the browser. However, it is not displayed in the IIS log:
· 401.1-Login failed.
　· Login failed due to 401.2-server configuration.

　· 401.3-The ACL is not authorized because of a resource limitation.
　· 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 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 permission settings on the file or folder on the server.

No access: IIS defines a number of different 403 errors. They indicate a more detailed cause of the error:
　· 403.1-run access is forbidden.
　· 403.2-Read access is forbidden.

　· 403.3-Write an interview is forbidden.
　· 403.4-Requires SSL.
　· 403.5-Requires SSL 128.
　· The 403.6-IP address is rejected.
　· 403.7-Requires client certificate.
　· 403.8-website access is denied.
　· 403.9-Excessive number of users.

　· 403.10-Invalid configuration.
　· 403.11-password changes.

　· 403.12-Deny access to the mapping table.

　· The 403.13-client certificate was revoked.
　· 403.14-Reject Folder list.
　· 403.15-Client access permission exceeded.

　· 403.16-client certificate is not trusted or invalid.

　· The 403.17-client certificate has expired or is not yet valid.
　· 403.18-The requested URL cannot be run in the current application pool.

This error code is specific to IIS 6.0.
　· 403.19-CGI cannot be run for the client in this application pool. This error code is dedicated to IIS 6.0.
　· 403.20-passport Login failed. This error code is specific to IIS 6.0.

· 404-not Found could not find the resource at the specified location. This is also a frequently used response.
　· 404.0-(None) – No files or folders found.

　· 404.1-Unable to access the Web site 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, etc.) does not apply to the specified resource, and the HTTP verb used to access this page is not agreed (the method is not agreed). [1.1]
· 406-not acceptable The specified resource has been found, but its MIME type is incompatible with the client specified in the Accpet header. The client browser does not accept the MIME type of the requested page. [1.1]
· 407-proxy authentication Required requires proxy authentication, similar to 401, to indicate that the client must be authorized by proxy server first.

[1.1]
· 408-request Timeout during the server license wait time, the customer has not issued any requests whatsoever. Customers can repeat the same request at a later time.

[1.1]
· 409-conflict is usually associated with a put request. The request cannot succeed because the request conflicts with the current state of the resource.

[1.1]
· 410-gone the requested document is no longer available, and the server does not know which address it should redirect to.

It differs from 404 in that returning 407 means that the document permanently leaves the specified location. And 404 indicates that the document is not available because of unknown reasons.

[1.1]
· 411-length Required Server cannot process the request. Unless the customer sends a content-length header.

[1.1]
· 412-precondition Failed Some of the prerequisites specified in the request header failed. [1.1]
· 413–request Entity Too Large the size of the target document exceeds the size that the server is currently willing to handle.

Assuming that the server feels that it can process the request later, it should provide a retry-after header.

[1.1]
· 414-request URI Too long URI. [1.1]
· 415– media types not supported.

· 416–requested Range not satisfiable server does not meet the Range header specified by the customer in the request. [1.1]
· 417– failed to run.
· 423– a locked error.

5xx-server Error
The server could not complete the request because it encountered an error.

· 500-internal Server Error Server encountered an unexpected situation and could not complete the client's request.
· 500.12-The application is busy launching again on the WEB server.
· 500.13-web server is too busy.

· 500.15-Do not agree to request Global.asa directly.
· 500.16–unc authorization credentials are not correct.

This error code is specific to IIS 6.0.
· The 500.18–url authorization store cannot be opened.

This error code is specific to IIS 6.0.

· 500.100-Internal ASP error.
· 501-not implemented server does not support the functionality required to implement the request. The header value specifies the configuration that is not implemented.

Like what. The customer issued a put request that is not supported by the server.

· When 502-bad Gateway server is acting as a gateways or proxy, ask for access to the next server in order to complete. However, the server returned an illegal response. It also says 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.
· 502.2-CGI Application error.
· The 503-service unavailable service is not available, and the server is unable to answer because of maintenance or heavy load.

Like what. The servlet may 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 specific to IIS 6.0.

· 504-gateway Timeout Gateway timed out. Used by the server acting as a proxy or gateway, indicating that the answer cannot be obtained in a timely manner from the remote server. [1.1]
· 505-http version not supported server it does not support the specified HTTP release number for the request.

[1.1]

Copyright notice: This article Bo Master original articles, blogs, without consent may not be reproduced.

HTTP response Code