HTTP Status Messages
When a browser requests services from a web server, errors may occur.
The following lists a series of HTTP status messages that may be returned:
1xx: Informational
Message |
Description |
100 Continue |
The server has received part of the request and, if it has not rejected it, the client should continue sending the rest of the request. |
101 Switching Protocols |
The server is switching protocols: the server will comply with the client's request to switch to another protocol. |
103 Checkpoint |
Used for recovery of failed PUT or POST requests when resuming. |
2xx: Success
Message |
Description |
200 OK |
The request was successful (this is the standard response for successful HTTP requests). |
201 Created |
The request has been fulfilled, resulting in the creation of a new resource. |
202 Accepted |
The request has been accepted for processing, but the processing has not been completed. |
203 Non-Authoritative Information |
The request was successful, but some response headers may be incorrect as they are from a copy of the document. |
204 No Content |
The request was successfully processed, but no new document was returned. The browser should continue displaying the original document. This status code is useful if a user regularly refreshes a page and the servlet can determine that the user's document is up to date. |
205 Reset Content |
The request was successfully processed, but no new document was returned. The browser should reset the content it is displaying. This is used to force the browser to clear form input content. |
206 Partial Content |
The client sent a GET request with a Range header, and the server fulfilled it. |
3xx: Redirection
Message |
Description |
300 Multiple Choices |
Multiple options. A list of links. The user can select a link to reach the destination. Up to five addresses are allowed. |
301 Moved Permanently |
The requested page has been moved to a new URL. |
302 Found |
The requested page has been temporarily moved to a new URL. |
303 See Other |
The requested page can be found under a different URL. |
304 Not Modified |
The document has not been modified as expected. The client has a cached version of the document and made a conditional request (usually providing an If-Modified-Since header indicating that the client only wants the document if it is newer than a specified date). The server informs the client that the cached document can still be used. |
305 Use Proxy |
The requested document should be retrieved through the proxy specified in the Location header. |
306 Switch Proxy |
This code is no longer used but is still reserved. |
307 Temporary Redirect |
The requested page has been temporarily moved to a new URL. |
308 Resume Incomplete |
Used for recovery of failed PUT or POST requests when resuming. |
4xx: Client Error
Message |
Description |
400 Bad Request |
Due to a syntax error, the server was unable to understand the request. |
401 Unauthorized |
A valid request, but access to the requested page is forbidden. The requested page requires authentication, and either the client did not provide it or the authentication failed. |
402 Payment Required |
This code is currently not in use. |
403 Forbidden |
A valid request, but access to the requested page is forbidden. |
404 Not Found |
The server could not find the requested page. |
405 Method Not Allowed |
The method specified in the request is not allowed. |
406 Not Acceptable |
The response generated by the server cannot be accepted by the client. |
407 Proxy Authentication Required |
The user must first authenticate using a proxy server for the request to be processed. |
408 Request Timeout |
The request timed out while waiting for the server. |
409 Conflict |
The request could not be completed due to a conflict. |
410 Gone |
The requested page is no longer available. |
411 Length Required |
"Content-Length" is not defined. The server will not accept the request without it. |
412 Precondition Failed |
A precondition given in the request was evaluated as false by the server. |
413 Request Entity Too Large |
The server will not accept the request because the request entity is too large. |
414 Request-URI Too Long |
The server will not accept the request because the URL is too long. This occurs when a POST request is converted to a GET request with a long query information. |
415 Unsupported Media Type |
The server will not accept the request because the media type is not supported. |
416 Requested Range Not Satisfiable |
The client requested a part of the document, but the server cannot provide the requested part. |
417 Expectation Failed |
The server cannot meet the requirements specified in the request header. |
5xx: Server Errors
Message: |
Description: |
500 Internal Server Error |
The request was not completed. The server encountered an unexpected condition. |
501 Not Implemented |
The request was not completed. The server does not support the functionality required to fulfill the request, or the server is unable to complete the request. |
502 Bad Gateway |
The request was not completed. The server, acting as a gateway or proxy, received an invalid response from the upstream server. |
503 Service Unavailable |
The server is currently unavailable (overloaded or down). |
504 Gateway Timeout |
Gateway timeout. The server, acting as a gateway or proxy, did not receive a timely response from the upstream server. |
505 HTTP Version Not Supported |
The server does not support the HTTP protocol version specified in the request. |
511 Network Authentication Required |
The user needs to provide authentication to gain network access. |