Common HTTP status codes：
2″ (the request succeeds) indicates that the request status code is successfully processed.
200 (success) server” has successfully processed the request. Usually, this means that the server provides the requested web page.
201 (created) request succeeded and the server created a new resource.
202″ (accepted) server has accepted the request, but it has not been processed.
203 (unauthorized information) server has successfully processed the request, but the information returned may come from another source.
204 (no content) server successfully handled the request, but did not return anything.
205 (reset content) server successfully handled the request, but did not return anything.
206″ (partial content) server successfully processed some GET requests.
3″ (the request is redirected) indicates that further operation is required to complete the request. Usually, these state codes are used for redirection.
300″ (multiple choices) requests the server to perform a variety of operations. The server can select an operation according to the requester (user agent), or provide a list of operations for the requester to choose.
302 (temporary mobile) server currently responds to requests from web pages in different locations, but the requester should continue to use the original location for future requests.
303 (see other locations) requester should retrieve the response using a separate GET request for different locations.
304″ has not been modified since the last request. When the server returns this response, it will not return the contents of the web page.
305″ request agent can only access the requested web page by proxy. If the server returns this response, it also indicates that the requestor should use the proxy.
307 (temporary redirection) server currently responds to requests from web pages in different locations, but the requester should continue to use the original location for subsequent requests.
400″ (wrong request) server does not understand the syntax of the request.
401″ (unauthorized) request for authentication. For web pages that need to be logged in, the server may return this response.
403″ prohibit requests from the server.
405 method disables the specified method in the request.
406″ does not accept the requested content feature to respond to the requested web page.
408″ (request timeout) occurs when the server waits for a request.
409″ server clashes when completing the request. The server must contain information about the conflict in the response.
411 (valid length required) server does not accept requests that do not contain valid content length header fields.
412 (not satisfying the prerequisite) server does not satisfy one of the prerequisites set by the requester in the request.
413 (request entity is too large) server can not process the request because the request entity is too large to handle the server.
414 (the requested URI is too long) is too long for the server to handle.
415″ (unsupported media type) is not supported by the requested page.
417 (unfulfilled expectation) server” is not satisfied. It expects “request header field”.
500″ (server internal error) server encountered an error and could not complete the request.
502 (error gateway) server acts as a gateway or proxy and receives an invalid response from the upstream server.
503 (service unavailable) server is currently unavailable (due to overload or downtime maintenance). Usually, this is only temporary.
504 (gateway timeout) servers act as gateways or proxies, but do not receive requests from upstream servers in time.
505 (HTTP version is not supported) server does not support the HTTP protocol version used in the request.
101 – Switching Protocols server converts compliance with a customer’s request to another protocol (HTTP 1.1 new)
2xx” – success
> 200 – OK is all right, and the reply document for GET and POST requests follows.
> 202 – Accepted has accepted the request, but the processing has not yet been completed.
203-Non-Authoritative Information document has returned normally, but some of the response headers may not be correct because they use a copy of the document, non-authoritative information (HTTP 1.1 new).
> 205 – Reset Content, but the browser should reset the content it displays. Used to force browsers to clear form input contents (HTTP 1.1 new).
206-Partial Content client sends a GET request (chunking request) with a Range header, and the server completes it (new HTTP 1.1).
3xx” – redirection
. 300 – Multiple Choices customers can be found in multiple locations that are listed in the returned document. If the server wants to give priority, it should be specified in the Location reply header.
. 302 – Found is similar to 301, but the new URL should be considered a temporary replacement, not a permanent one. Note that the corresponding state information in HTTP1.0 is “Moved Temporatily”. When the status code appears,Browsers
.303-See Other is similar to 301/302, except that if the original request is POST, the redirection target document specified by the Location header should be extracted by GET (HTTP 1.1 new).
. 304 – Not Modified client has buffered documents and makes a conditional request (typically providing an If-Modified-Since header to indicate that the client only wants documents updated on a specified date). The server tells the customer the original buffer.A
. 305-Use Proxy customers should be extracted through the proxy server specified in the Location header (HTTP 1.1 new).
4xx” client error
> 400 – Bad Request.
. 401 – Unauthorized access was denied, and the client attempted unauthorized access to password-protected pages. A WWW-Authenticate header is included in the response, and the browser displays the user name/password dialog box accordingly, and then fills inclose
> 401.1 – login failed.
” > 401.2 server configuration failed to log in.
> 401.4 filter failed.
> 401.5 – ISAPI/CGI failed.
> > 401.7 access is denied by the URL authorization policy on the Web server. This error code is dedicated to IIS 6.
> > 403.2 — access to reading is prohibited.
> > 403.3 – write access is prohibited.
– SSL 128.
> 403.7 – requires client certificate.
> 403.8. Site visit denied.
> 403.10 – configuration is invalid.
> > 403.11 – password changes.
> 403.13 – client certificate was revoked.
> 403.15 – exceeding client access permission.
> 403.17 client certificate has expired or has not yet entered into force.
> 403.19 – can not execute CGI for the client in this application pool. This error code is dedicated to IIS 6.
> 403.20 – Passport failed. This error code is dedicated to IIS 6.
> 404 – (no) – no documents or catalogues were found.
> 404.2 — Web service extension lock strategy prevents this request.
. 405 – Method Not Allowed Request Method (GET, POST, HEAD, DELETE, PUT, TRACE, etc.) does not apply to the specified resource, and HTTP predicates used to access this page are not allowed (square)Law is not allowed) (HTTP 1.1
” new “
. 406 – Not Acceptable specified resource has been found, but its MIME type is incompatible with what the client specified in the Accpet header, and the client browser does not accept the MIME type of the requested page (new HTTP 1.1).
407-Proxy Authentication Required requires proxy authentication, similar to 401, which means that the client must first be authorized by the proxy server. (HTTP 1.1 new)
408 – Request Timeout in the server license waiting time, the customer has not issued any request. Customers can repeat the same request later. (HTTP 1.1 new)
. 410 – The document requested by Gone is no longer available, and the server does not know which address to redirect to. It differs from 404 in that returning 407 means that the document has permanently left the specified location, while 404 means that it is unknown
411-Length Required server cannot process requests unless the client sends a Content-Length header. (HTTP 1.1 new)
412-Precondition Failed request header failed (HTTP 1.1 new).
413 — Request Entity Too Large target document is larger than the server is currently willing to handle. If the server thinks that it can handle the request later, it should provide a Retry-After header (HTTP 1.1
> 414 – Request URI Too Long URI is too long (HTTP 1.1 new).
416 Requested Range Not Satisfiable server cannot satisfy the Range header specified by the client in the request. (HTTP 1.1 new) 417 – failed in implementation.
5xx server error”
. 500 – Internal Server Error server encountered unexpected circumstances, unable to complete customer requests.
> > 500.12 — the application is busy restarting on the Web server.
” 500.13. Web server is too busy.
> 500.16 – UNC is incorrect. This error code is dedicated to IIS 6.
> 500.18 – URL cannot be opened. This error code is dedicated to IIS 6.
501 – Not Implemented server does not support the functionality required to implement the request, and the header value specifies the unrealized configuration. For example, a PUT request that the server does not support is issued by the client.
502 – Bad Gateway server acts as a gateway or proxy, it accesses the next server to complete the request, but the server returns an illegal response. Also said that the Web server received invalid response when it was used as gateway or proxy server.
>.
> 502.2 – CGI application.
. 503 – Service Unavailable service is unavailable, and the server cannot respond due to maintenance or overload. For example, Servlet may return 503 when the database connection pool is full. When the server returns 503, it can provideOne
Retry-After”. This error code is dedicated to IIS 6.
504-Gateway Timeout gateway timeout, used by a server acting as a proxy or gateway, indicates that a response cannot be received from a remote server in a timely manner. (HTTP 1.1 new).
