Understand HTTP errors

This guide helps you understand the various HTTP status codes.

1xx - Information

error 100: Continue
The server has received the request headers and the client may continue to send the request body.

error 101: Switching Protocols
The server agrees to switch protocols as requested by the client.

2xx - Success

error 200: Request successful
The request has been successfully processed by the server.

error 201: Document created (reason: new URI)
The request was successful and resulted in the creation of a new resource.

error 202: Request completed asynchronously (TBS)
The request has been accepted but processing is not yet complete.

error 203: Incomplete request
The server successfully processed the request, but the information returned comes from a third-party source.

error 204: No Content
The request was successfully processed, but there is no content to return.

error 205: Request completed but form empty
The server has successfully processed the request and asks the client to reset the document that submitted the request.

error 206: Incomplete GET request
The server returns only part of the data, as requested by the client with the Range header.

3xx - Redirections

error 300: The server cannot determine the return code
The request has several possible responses, and the server cannot automatically choose one of them.

error 301: Moved Permanently
The requested resource has been permanently moved to a new URL.

error 302: Document temporarily moved
The requested resource is temporarily located at a different URL.

error 303: Redirection with new access method
The response to the request can be found under another URL using a GET method.

Error 304: The field 'If-Modified-Since' was not modified
The resource has not been modified since the last request. No new data will be sent.

Error 305: Redirect to a proxy specified by the header
The requested resource must be accessed through a specified proxy.

Error 307: Temporary Redirect
The requested resource temporarily resides under a different URL, but the client must use the same method to make the next request.

4xx - Client Errors

Error 400: Bad request
The request is incorrect or malformed.

error 401: No authorization to access the document
Access to the resource requires authentication.

error 402: Payment required
This code is reserved for future use regarding online payments.

Error 403: Forbidden
The server understands the request but refuses to authorize it.

Error 404: The requested page does not exist
The server cannot find the requested resource.

Error 405: Method Not Allowed
The method specified in the request is not allowed for the target resource.

Error 406: Request not acceptable by the server
The requested resource is not capable of generating acceptable content according to the Accept headers sent in the request.

Error 407: Proxy Authentication Required
Access to the resource requires authentication by a proxy.

Error 408: Request timeout
The server did not receive the complete request within the time allowed.

error 409: The user must resubmit with more information
The request cannot be processed due to a conflict with the current state of the resource.

Error 410: This resource is no longer available
The requested resource is no longer available and this is permanent.

error 411: The server refused the request because it has no length
The server refuses to process the request without a valid Content-Length header.

Error 412: The precondition given in the request has failed
One of the conditions specified in the request headers has failed.

Error 413: The request entity was too large
The server refuses to process the request because the size of the entity is too large.

Error 414: The request URI was too long
The server refuses to process the request because the URI is too long.

Error 415: Unsupported Media Type
The server refuses to process the request because the format of the request entity is not supported.

5xx - Server Errors

Error 500: Internal Server Error
The server encountered an unexpected condition that prevented it from fulfilling the request.

error 501: Requested feature not supported by server
The server does not support the functionality required to process the request.

Error 502: Bad Gateway
The server, acting as a gateway or proxy, received an invalid response from the upstream server.

Error 503: Service Unavailable
The server is not available at the moment (overloaded or maintenance).

Error 504: Gateway Timeout
The server, acting as a gateway or proxy, did not receive a timely response from the upstream server.

Error 505: HTTP Version Not Supported
The server does not support the HTTP protocol version used in the request.