HTTP Status Hub

HTTP Status Codes

Complete reference for all standard HTTP response status codes with detailed explanations, code examples, and fix solutions.

1xx Informational

The server has received the request headers, and the client should proceed to send the request body.

Switching Protocols

The server is switching protocols as requested by the client.

The server has received and is processing the request, but no response is available yet.

The server sends preliminary hints before the final response.

2xx Success

The request has succeeded. The information returned depends on the method used in the request.

The request has been fulfilled and resulted in a new resource being created. Typically used for POST requests.

The request has been accepted for processing, but the processing has not been completed.

Non-Authoritative Information

The returned meta-information is not from the origin server but from a local or third-party copy.

The server successfully processed the request but is not returning any content.

The server successfully processed the request and asks the client to reset the document view.

Partial Content

The server is delivering only part of the resource due to a range header sent by the client.

The message body contains multiple status codes for multiple independent operations.

Already Reported

The members of a DAV binding have already been enumerated in a previous reply.

The server has fulfilled a GET request and the response represents the result of instance manipulations.

3xx Redirection

Multiple Choices

The request has more than one possible response. The user should choose one of them.

Moved Permanently

The requested resource has been permanently moved to a new URL. Search engines will update their links.

The requested resource resides temporarily at a different URL.

The response to the request can be found under a different URI using GET method.

The resource has not been modified since the last request. Client can use cached version.

Temporary Redirect

The request should be repeated with another URI, but future requests should still use the original URI.

Permanent Redirect

The request and all future requests should be repeated using another URI.

4xx Client Error

The server cannot process the request due to malformed syntax or invalid request message framing.

Authentication is required. The request lacks valid authentication credentials.

Payment Required

Reserved for future use. Originally intended for digital payment systems.

The server understood the request but refuses to authorize it.

The server cannot find the requested resource. The URL may be incorrect or the resource deleted.

Method Not Allowed

The request method is not supported for the requested resource.

The server cannot produce a response matching the list of acceptable values in the request headers.

Proxy Authentication Required

The client must first authenticate itself with the proxy.

Request Timeout

The server timed out waiting for the request from the client.

The request conflicts with the current state of the target resource.

The requested resource is no longer available and will not be available again.

Length Required

The server requires a Content-Length header in the request.

Precondition Failed

The server does not meet one of the preconditions specified in the request headers.

Content Too Large

The request body is larger than the server is willing or able to process.

The URI provided was too long for the server to process.

Unsupported Media Type

The server refuses to accept the request because the media type is not supported.

Range Not Satisfiable

The requested range cannot be satisfied by the server.

Expectation Failed

The server cannot meet the requirements of the Expect request-header field.

The server refuses to brew coffee because it is a teapot. This is an April Fools' joke from RFC 2324.

Misdirected Request

The request was directed at a server that is not able to produce a response.

Unprocessable Content

The server understands the content type but was unable to process the contained instructions.

The resource that is being accessed is locked.

Failed Dependency

The request failed because it depended on another request that failed.

The server is unwilling to risk processing a request that might be replayed.

Upgrade Required

The server refuses to perform the request using the current protocol.

Precondition Required

The origin server requires the request to be conditional.

Too Many Requests

The user has sent too many requests in a given amount of time (rate limiting).

Request Header Fields Too Large

The server is unwilling to process the request because its header fields are too large.

Unavailable For Legal Reasons

The server is denying access to the resource as a consequence of a legal demand.

5xx Server Error

Internal Server Error

The server encountered an unexpected condition that prevented it from fulfilling the request.

Not Implemented

The server does not support the functionality required to fulfill the request.

The server acting as a gateway received an invalid response from an upstream server.

Service Unavailable

The server is currently unable to handle the request due to maintenance or overloading.

Gateway Timeout

The server acting as a gateway did not receive a timely response from the upstream server.

HTTP Version Not Supported

The server does not support the HTTP protocol version used in the request.

Variant Also Negotiates

The server has an internal configuration error during content negotiation.

Insufficient Storage

The server is unable to store the representation needed to complete the request.

The server detected an infinite loop while processing the request.

Further extensions to the request are required for the server to fulfill it.

Network Authentication Required

The client needs to authenticate to gain network access.