HTTP status Rollup

Common HTTP status Code (OK) moved Permanently 302 Found 304 not Modified 307 temporary-Redirect bad Request 401 Unauthorized 403 Forbidden 404 Not Found 410 Gone-Internal Server Error 501 Not implementedMB Continue
The initial request has been accepted and the customer should continue to send the remainder of the request Protocols switching
The server converts the client's request to a different protocol OK
Everything is fine, the answer document for Get and post requests follows 201 Created
The server has created the document, and the location header gives its URL. accepted
The request has been accepted, but processing has not been completed. 203 non-authoritative Information
The document has returned normally, but some of the answer headers may not be correct because a copy of the document is being used 204 No Content
The browser should continue to display the original document without a new 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
There is no new content, but the browser should reset what it displays. Used to force the browser to clear form input 206 Partial Content
The customer sends a GET request with a range header, and the server completes its Multiple choices
The documents requested by the client 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. permanently moved
The client requests a document elsewhere, the new URL is given in the location header, and the browser should automatically access the new URL. 302 Found
Similar to 301, but the new URL should be considered temporary instead of permanent. 303 and other
Similar to 301/302, the difference is that if the original request is post,location header specified redirect target document should be extracted by get 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
The document requested by the customer should be extracted via the proxy server specified in the location header 307 Temporary Redirect
Same as 302 (Found). 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. Bad Request
A syntax error occurred on the request. 401 Unauthorized
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. 403 Forbidden
The resource is not available. 404 Not Found
Unable to find the resource at the specified location 405 Method Not allowed
The request method (get, POST, head, Delete, put, Trace, and so on) does not apply to the specified resource. 406 Not acceptable
The specified resource has been found, but its MIME type is incompatible with the customer specified in the Accpet header 407 Proxy Authentication Required
Similar to 401 indicates that the customer must first be authorized by the proxy server. 408 Request Timeout
The customer has not made any requests during the wait time that the server has allowed. Customers can repeat the same request at a later time. 409 Conflict
Usually associated with put requests. The request cannot succeed because the request and the current state of the resource are conflicting. 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. 411 Length Required
The server cannot process the request unless the customer sends a content-length header. 412 Precondition Failed
Some prerequisites specified in the request header failed 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 414 Request URI Too Long
URI is too long 416 requested Range not satisfiable
The server does not meet the range header specified by the customer in the request Internal Server Error
The server encountered an unexpected situation and could not complete the customer's request 501 Not implemented
The server does not support the functionality required to implement the request. For example, the customer issued a put request that the server does not support 502 Bad Gateway
When the server acts as a gateway or proxy, it accesses the next server in order to complete the request, but the server returns an illegal answer 503 Service Unavailable
The server failed to answer due to maintenance or overload. For example, a servlet might return 503 if the database connection pool is full. A retry-after header can be supplied when the server returns 503 504 Gateway Timeout
Used by a server acting as a proxy or gateway, indicating that an answer cannot be received from a remote server in a timely manner 505 HTTP Version not supported
The server does not support the HTTP version specified in the request