HTTP return status codes and meanings

"100″: Continue (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 (switching protocol) The requestor has asked the server to switch protocols and the server has confirmed and is ready to switch." (HTTP 1.1 new)

"200″: Ok (success) Everything is fine, the answer document for Get and post requests is followed.

"201″: Created (created) the server has created the document, and the location header gives its URL.

"202″: Accepted (accepted) the server has accepted the request, but it has not been processed.

The 203″: non-authoritative information (unauthorized information) document has returned normally, but some of the answer headers may be incorrect and may come from another source. (HTTP 1.1 new).

"204″: No Content (Nothing) returns Nothing, the browser should continue to display the original document.

"205″: Reset content does not have new content, but the browser should reset what it displays." Used to force the browser to clear the form input (HTTP 1.1 new).

"206″: Partial content (partial) server successfully processed some GET requests. (HTTP 1.1 new)

"300″: Multiple Choices (multiple choices) the documents requested by the customer can be found in multiple locations that have been 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 (permanently moved) The requested page has been permanently moved to a new location. When the server returns this response (as a response to a GET or HEAD request), the requestor is automatically forwarded to the new location.

"302″: Found (temporary move) is similar to 301, but the new URL should be treated as a temporary replacement instead of permanent." Note that the corresponding status information in HTTP1.0 is "Moved temporatily", and when the 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 used with 301 substitutions. For example, if 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 automatically redirect only if the original request is get. See 307.

"303″: See other (View other locations) is similar to 301/302, except that if the original request is post,location the redirect destination document specified by the header should be fetched via get (HTTP 1.1 new).

"304″: Not Modified (unmodified) The requested webpage has not been modified since the last request. The original buffered document can also continue to be used and will not return the page content.

"305″: Use proxy (using proxies) can only use proxy access to requested Web pages. If the server returns this response, the server also indicates which proxy the requestor should use. (HTTP 1.1 new)

"307″: Temporary Redirect (temporary redirection) 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 be redirected only if the answer to the POST request is 303. For this reason, HTTP 1.1 has been added in 307 to allow for more cleanup of the region in several status codes: When a 303 response occurs, the browser can follow the redirected get and post requests, and if the 307 answer, the browser can only follow the redirect to the GET request. (HTTP 1.1 new)

"400″: A syntax error occurred with bad request request.

"401″: Unauthorized (Unauthorized) customer attempted to access a password-protected page without authorization. A www-authenticate header is included in the answer, and the browser displays the user name/Password dialog box, and then makes a request again after filling in the appropriate authorization header.

"403″: Forbidden (Disabled) resource is not available. The server understands the customer's request, but refuses to process it. This is usually caused by the permissions set on the file or directory on the server.

"404″: Not Found (not found) could not find the resource at the specified location.

"405″: Method not allowed (methods disabled) The request method (GET, POST, HEAD, DELETE, PUT, trace, etc.) is disabled. (HTTP 1.1 new)

"406″: Not acceptable (not accepted) The specified resource has been found, but its MIME type is incompatible with the client specified in the Accpet header (HTTP 1.1 new).

The 407″: Proxy authentication Required (requires proxy authorization) is similar to 401, indicating that the client must be authorized by the proxy server first. (HTTP 1.1 new)

"408″: Request time-out (requests timed out) the server timed out while waiting for the request. (HTTP 1.1 new)

"409″: Conflict (conflict) is usually associated with a put request. The request cannot succeed because the request conflicts with the current state of the resource. (HTTP 1.1 new)

"410″: Gone (Deleted) If the requested resource has been permanently deleted, the server returns this response. This code is similar to the 404 (not Found) code, but sometimes replaces the 404 code in cases where resources have previously existed but are no longer present. If the resource has been permanently deleted, you should use 301 code to specify a new location for the resource. (HTTP 1.1 new)

"411″: Length Required (requires valid length) does not accept requests that contain invalid content-Length header fields. (HTTP 1.1 new)

"412″: Precondition Failed (precondition not met) the server did not meet one of the prerequisites set by the requestor in the request. (HTTP 1.1 new)

"413″: Request entity Too Large (Request entity is too large) requests entities are too large to exceed the processing power of the server. If the server thinks it can process the request later, it should provide a retry-after header. (HTTP 1.1 new)

"414″: Request-uri Too Large (The requested URI is too long) The requested URI (usually the URL) is too long for the server to process.

"415″: Unsupported media type (not supported) The requested format is not supported by the requested page.

"416″: Requested range not satisfiable (request scope does not meet requirements) the server does not meet the range header specified by the customer in the request. (HTTP 1.1 new)

"417″: Expectation Failed (unmet expectations) the server did not meet the requirements of the" expected "Request header field.

"500″: Internal Server error (server internal errors) the servers encountered an error and could not complete the request.

"501″: Not implemented (not implemented) the server does not have the ability to complete the request. For example, the server may return this code when the server does not recognize the request method.

"502″: Bad Gateway" when the server acts as a gateway or proxy, the server returns an illegal response in order to complete the request to access the next server.

"503″: Service Unavailable (services unavailable) server failed to answer due to maintenance or heavy load. Usually, this is just a temporary state.

"504″: Gateway time-out (gateways timeout) is used by a server acting as a proxy or gateway, indicating that a reply cannot be received from a remote server in a timely manner. (HTTP 1.1 new)

"505″: HTTP version not supported (HTTP versions unsupported) does not support the HTTP protocol version used in the request.

HTTP return status codes and meanings