HTTP Status Code Reference
Browse and search all HTTP status codes with descriptions
1xx Informational
The server has received the request headers and the client should proceed to send the request body.
The server is switching protocols as requested by the client via the Upgrade header.
The server has received and is processing the request, but no response is available yet.
Used to return some response headers before the final HTTP message.
2xx Success
The request has succeeded. The meaning depends on the HTTP method used.
The request has been fulfilled and a new resource has been created.
The request has been accepted for processing, but the processing has not been completed.
The returned metadata is not exactly the same as available from the origin server.
The server successfully processed the request but is not returning any content.
The server successfully processed the request and is not returning any content, and requires the requester to reset the document view.
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.
The members of a DAV binding have already been enumerated in a previous reply.
3xx Redirection
The request has more than one possible response. The user or user agent should choose one.
The URL of the requested resource has been changed permanently. The new URL is given in the response.
The URI of requested resource has been changed temporarily. Further changes might be made in the future.
The server sent this response to direct the client to get the requested resource at another URI with a GET request.
The response has not been modified, so the client can continue to use the cached version.
The requested resource is available only through a proxy, the address for which is provided in the response.
The server sends this response to direct the client to get the requested resource at another URI with the same method.
The resource is now permanently located at another URI, specified in the Location header.
4xx Client Error
The server cannot process the request due to something perceived to be a client error.
The client must authenticate itself to get the requested response.
Reserved for future use. Originally created for digital payment systems.
The client does not have access rights to the content; the server is refusing to give the requested resource.
The server cannot find the requested resource. The URL is not recognized.
The request method is known by the server but is not supported by the target resource.
The server cannot produce a response matching the list of acceptable values defined in the request headers.
The client must first authenticate itself with the proxy.
The server timed out waiting for the request.
The request conflicts with the current state of the server.
The requested content has been permanently deleted from the server with no forwarding address.
The server rejected the request because the Content-Length header field is not defined.
The client has indicated preconditions in its headers which the server does not meet.
The request entity is larger than limits defined by the server.
The URI requested by the client is longer than the server is willing to interpret.
The media format of the requested data is not supported by the server.
The range specified by the Range header field in the request cannot be fulfilled.
The expectation indicated by the Expect request header field cannot be met by the server.
The server refuses the attempt to brew coffee with a teapot (RFC 2324).
The request was directed at a server that is not able to produce a response.
The request was well-formed but was unable to be followed due to semantic errors.
The resource that is being accessed is locked.
The request failed because it depended on another request that failed.
The server is unwilling to risk processing a request that might be replayed.
The server refuses to perform the request using the current protocol but might after the client upgrades.
The origin server requires the request to be conditional.
The user has sent too many requests in a given amount of time (rate limiting).
The server is unwilling to process the request because its header fields are too large.
The user agent requested a resource that cannot legally be provided.
5xx Server Error
The server has encountered a situation it does not know how to handle.
The request method is not supported by the server and cannot be handled.
The server, while acting as a gateway, got an invalid response from the upstream server.
The server is not ready to handle the request, often due to maintenance or overloading.
The server is acting as a gateway and cannot get a response in time from the upstream server.
The HTTP version used in the request is not supported by the server.
The server has an internal configuration error: transparent content negotiation results in a circular reference.
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.
The client needs to authenticate to gain network access.