Common HTTP Status Codes
-
- 200 OK
-
- 301 moved permanently
- 302 found
-
- 304 not modified
-
- 307 temporary redirect
- 400 bad request
-
- 401 unauthorized
-
- 403 Forbidden
- 404 not found
-
- 410 gone
-
- 500 Internal Server Error
- 501 not implemented
100 continue
The initial request has been accepted, and the customer should continue to send the remaining part of the request 101 switching protocols
The server converts a client-compliant request to another protocol 200 OK
Everything works. The response document for get and post requests follows 201 created.
The server has created a document and the location header provides its URL. 202 accepted
The request has been accepted, but the processing has not been completed. 203 non-authoritative information
The document has been returned normally, but some response headers may be incorrect, because the 204 NO content copy of the document is used.
If no new document exists, the browser should continue to display the original document. If the user regularly refreshes the page, and the servlet can determine that the user document is new enough, this status Code Is a useful 205 reset content
There is no new content, but the browser should reset the content it shows. Used to force the browser to clear the form input 206 partial content
The client sends a GET request with a range header, and the server completes its 300 multiple choices
Documents requested by the customer can be found in multiple locations, which are listed in the returned documents. If the server needs to give priority, it should be specified in the location response header. 301 moved permanently
The document requested by the customer is elsewhere. The new URL is provided in the location header, and the browser should automatically access the new URL. 302 found
Similar to 301, but the new URL should be treated as a temporary alternative, rather than permanent. 303 see other
Similar to 301/302, the difference is that if the original request is post, the redirection target document specified by the location header should use get to extract 304 not modified
The client has a buffered document and sends a conditional request (generally, the IF-modified-since header is provided to indicate that the customer only wants to update the document on a specified date ). The server tells the customer that the original buffer documentation can still be used. 305 use proxy
The document requested by the customer should be extracted by 307 temporary redirect using the proxy server specified by the location header
It is the same as 302 (found. Many browsers mistakenly respond to the 302 response for redirection. Even if the original request is post, it can only be redirected when the POST request actually responds to 303. For this reason, HTTP 1.1 adds 307 to clear the region code in several states: When a 303 response occurs, the browser can follow the redirected get and post requests; if a 307 response occurs, the browser can only follow the redirection to get requests. 400 bad request
The request has a syntax error. 401 unauthorized
The customer attempted to access the password-protected page without authorization. The response contains a WWW-Authenticate header. the browser displays the username/password dialog box accordingly, and then sends a request again after entering the appropriate authorization header. 403 Forbidden
Resource unavailable. 404 not found
Resource 405 method not allowed at the specified position cannot be found
Request methods (get, post, Head, delete, put, Trace, etc.) are not applicable to specified resources. 406 not acceptable
The specified resource has been found, but its MIME type is not compatible with the 407 proxy authentication required specified in the accpet header.
Similar to 401, the customer must first be authorized by the proxy server. 408 request timeout
The customer has not issued any request within the waiting time of the server license. The customer can repeat the same request later. 409 conflict
It is usually related to put requests. The request cannot be successful because the request conflicts with the current status of the resource. 410 gone
The requested document is no longer available and the server does not know which address to redirect. It differs from 404 in that if 407 is returned, the document permanently leaves the specified position, and 404 indicates that the document is unavailable for unknown reasons. 411 length required
The server cannot process the request unless the client sends a Content-Length header. 412 precondition failed
Some of the prerequisites specified in the request header fail: 413 Request Entity too large
The size of the target document exceeds the size that the server is willing to process. If the server considers that it can process the request later, it should provide a retry-after header 414 request URI Too Long
The URI is too long. 416 requested range not satisfiable
The server cannot meet the range header 500 internal server error specified by the customer in the request.
The server encountered unexpected circumstances and could not complete the customer's request 501 not implemented
The server does not support the functions required to implement the request. For example, the customer sends a put request 502 Bad Gateway that is not supported by the server.
When the server acts as a gateway or proxy, in order to complete the request to access the next server, but the server returns an invalid response 503 service unavailable
The server fails to respond due to maintenance or heavy load. For example, Servlet may return 503 when the database connection pool is full. When the server returns 503, A retry-after header 504 gateway timeout can be provided.
Used by a proxy or gateway server, indicating that the server cannot receive a response from the remote server in a timely manner. 505 HTTP Version Not Supported
The server does not support the HTTP Version specified in the request
