Quick reference guide
A comprehensive guide to all HTTP status codes with detailed descriptions, examples, and common use cases for developers.
Showing 58 status codes
The server has received the request headers and the client should proceed to send the request body.
The requester has asked the server to switch protocols and the server has agreed to do so.
The server has received and is processing the request, but no response is available yet.
Used to return some response headers before final HTTP message.
The request has succeeded. The meaning of success depends on the HTTP method used.
The request has been fulfilled and resulted in a new resource being created.
The request has been accepted for processing, but the processing has not been completed.
The request was successful but the enclosed payload has been modified by a transforming proxy.
The server successfully processed the request and is not returning any content.
The server successfully processed the request and is instructing the client to reset the document view.
The server is delivering only part of the resource due to a range header sent by the client.
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 in the URI might be made.
The server sent this response to direct the client to get the requested resource at another URI with a GET request.
Indicates that the resource has not been modified since the version specified by the request headers.
The server sends this response to direct the client to get the requested resource at another URI with same method.
The resource is now permanently located at another URI, specified by the Location header.
The server cannot or will not process the request due to something that is perceived to be a client error.
The client must authenticate itself to get the requested response.
Reserved for future use. Originally intended for digital payment systems.
The client does not have access rights to the content; that is, it is unauthorized.
The server can not find the requested resource. This is one of the most famous status codes.
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 request headers.
The client must first authenticate itself with the proxy.
The server would like to shut down this unused connection.
The request conflicts with the current state of the server.
The requested content has been permanently deleted from server, with no forwarding address.
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.
Request entity is larger than limits defined by 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. This is an April Fools joke from 1998.
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 due to failure of a previous request.
Indicates that the server is unwilling to risk processing a request that might be replayed.
The server refuses to perform the request using the current protocol.
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 requests an illegal resource, such as a web page censored by a government.
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 working as a gateway, got an invalid response from the upstream server.
The server is not ready to handle the request, usually due to maintenance or overload.
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.
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.