HTTP Status Codes
v1.0.0Browse all HTTP status codes with meaning, RFC reference, and usage guidance.
61 codes found
The server has received the request headers and the client should proceed to send the request body.
RFC 9110
The requester has asked the server to switch protocols and the server is acknowledging that it will do so.
RFC 9110
The server has received and is processing the request, but no response is available yet.
RFC 2518
Used to return some response headers before the final HTTP message.
RFC 8297
The request has succeeded. The meaning of the success depends on the HTTP method.
RFC 9110
The request has succeeded and a new resource has been created as a result.
RFC 9110
The request has been received but not yet acted upon. It is non-committal.
RFC 9110
The returned meta-information is not exactly the same as is available from the origin server.
RFC 9110
The server successfully processed the request and is not returning any content.
RFC 9110
The server successfully processed the request, but is not returning any content. The client should reset the document view.
RFC 9110
The server is delivering only part of the resource due to a range header sent by the client.
RFC 9110
The message body that follows is by default an XML message and can contain a number of separate response codes.
RFC 4918
The members of a DAV binding have already been enumerated in a preceding part of the response.
RFC 5842
The server has fulfilled a GET request for the resource, and the response is a representation of the result of one or more instance-manipulations.
RFC 3229
The request has more than one possible response.
RFC 9110
The URL of the requested resource has been changed permanently. The new URL is given in the response.
RFC 9110
The URI of requested resource has been changed temporarily.
RFC 9110
The server sent this response to direct the client to get the requested resource at another URI with a GET request.
RFC 9110
This is used for caching purposes. It tells the client that the response has not been modified.
RFC 9110
The server sends this response to direct the client to get the requested resource at another URI with the same method.
RFC 9110
The resource is now permanently located at another URI. Method and body are preserved.
RFC 7538
The server cannot or will not process the request due to something that is perceived to be a client error.
RFC 9110
The client must authenticate itself to get the requested response.
RFC 9110
Reserved for future use. Currently used by some APIs for payment paywalls.
RFC 9110
The client does not have access rights to the content. Unlike 401, the client's identity is known.
RFC 9110
The server cannot find the requested resource.
RFC 9110
The request method is known by the server but is not supported by the target resource.
RFC 9110
The server cannot produce a response matching the list of acceptable values defined in the request's headers.
RFC 9110
Authentication is needed to be done by a proxy.
RFC 9110
The server would like to shut down this unused connection.
RFC 9110
The request conflicts with the current state of the server.
RFC 9110
The requested content has been permanently deleted from server, with no forwarding address.
RFC 9110
Server rejected the request because the Content-Length header field is not defined.
RFC 9110
The client has indicated preconditions in its headers which the server does not meet.
RFC 9110
Request entity is larger than limits defined by server.
RFC 9110
The URI requested by the client is longer than the server is willing to interpret.
RFC 9110
The media format of the requested data is not supported by the server.
RFC 9110
The range specified by the Range header field in the request cannot be fulfilled.
RFC 9110
The expectation indicated by the Expect request header field cannot be met by the server.
RFC 9110
The server refuses the attempt to brew coffee with a teapot. An April Fools joke from RFC 2324.
RFC 2324
The request was directed at a server that is not able to produce a response.
RFC 9110
The request was well-formed but was unable to be followed due to semantic errors.
RFC 9110
The resource that is being accessed is locked.
RFC 4918
The request failed because it depended on another request and that request failed.
RFC 4918
Indicates that the server is unwilling to risk processing a request that might be replayed.
RFC 8470
The server refuses to perform the request using the current protocol.
RFC 9110
The origin server requires the request to be conditional.
RFC 6585
The user has sent too many requests in a given amount of time (rate limiting).
RFC 6585
The server is unwilling to process the request because its header fields are too large.
RFC 6585
The user agent requested a resource that cannot legally be provided.
RFC 7725
The server has encountered a situation it does not know how to handle.
RFC 9110
The request method is not supported by the server and cannot be handled.
RFC 9110
The server, while working as a gateway, got an invalid response from the upstream server.
RFC 9110
The server is not ready to handle the request. Common causes are a server that is down for maintenance or overloaded.
RFC 9110
The server is acting as a gateway and cannot get a response in time.
RFC 9110
The HTTP version used in the request is not supported by the server.
RFC 9110
The server has an internal configuration error: transparent content negotiation results in a circular reference.
RFC 2295
The method could not be performed on the resource because the server is unable to store the representation needed to successfully complete the request.
RFC 4918
The server detected an infinite loop while processing the request.
RFC 5842
Further extensions to the request are required for the server to fulfil it.
RFC 2774
Indicates that the client needs to authenticate to gain network access.
RFC 6585