HTTP Status Messages

When a browser requests service from a web server, an error may occur.

The following lists a series of HTTP status messages that may be returned:

1xx: Informational

Message: Description:
100 Continue The server has only received a partial request. If the server has not rejected the request, the client should continue sending the rest of the request.
101 Switching Protocols Server Switching Protocols: The server will switch to another protocol in accordance with the client's request.
103 Checkpoint Used in the resumable requests proposal to resume aborted PUT or POST requests.

2xx: Success

Message: Description:
200 OK Request successful (This is the standard response to a successful HTTP request.)
201 Created The request has been fulfilled, and a new resource has been created.
202 Accepted The request for processing has been accepted, but the processing has not been completed.
203 Non-Authoritative Information The request has been successfully processed, but some response headers may be incorrect because a copy of another document is used.
204 No Content The request has been successfully processed, but no new document was returned. The browser should continue to display the original document. If the user periodically refreshes the page, and the Servlet can determine that the user's document is fresh enough, this status code is very useful.
205 Reset Content The request has been successfully processed, but no new document was returned. However, the browser should reset the content it displays. Used to force the browser to clear form input.
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 choices. 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 at a different URL.
304 Not Modified The document has not been modified as expected. The client has a cached document and has issued a conditional request (usually providing an If-Modified-Since header to indicate that the client only wants documents newer than the specified date). The server tells the client that the originally cached document can continue to be used.
305 Use Proxy The document requested by the client should be retrieved through the proxy server specified by the Location header.
306 Switch Proxy Currently no longer used, but the code is still reserved.
307 Temporary Redirect The requested page has been temporarily moved to a new URL.
308 Resume Incomplete Used in the resumable requests proposal to resume aborted PUT or POST requests.

4xx: Client Error

Message: Description:
400 Bad Request The server could not understand the request due to a syntax error.
401 Unauthorized The request is valid, but access to the requested page is forbidden because the requested page requires authentication, and the client did not provide it or authentication failed.
402 Payment Required This code is not yet available for 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 with the proxy server so that the request will be processed.
408 Request Timeout The request exceeded the server's waiting time.
409 Conflict The request could not be completed due to a conflict.
410 Gone The requested page is unavailable.
411 Length Required "Content-Length" is not defined. Without this, the server will not accept the request.
412 Precondition Failed The precondition in the request was evaluated as failed by the server.
413 Request Entity Too Large The server will not accept the request because the requested 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 very long query string.
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 partial document, but the server cannot provide the requested part.
417 Expectation Failed The server cannot satisfy the request header specified by the client in the request.

5xx: Server Error

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 requested functionality, or the server cannot complete the request.
502 Bad Gateway The request was not completed. When the server acted as a gateway or proxy, it received an invalid response from the upstream server.
503 Service Unavailable The server is currently unavailable (overloaded or down).
504 Gateway Timeout Gateway timeout. When the server acted as a gateway or proxy, it failed to 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 obtain network access.
Other extensions