HTTP Status Code Lookup

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 succeeded. The meaning of the success depends on the HTTP method.

The request succeeded, and a new resource was created as a result.

The request has been received but not yet acted upon. It is noncommittal.

The returned metadata is not exactly the same as is available from the origin server.

There is no content to send for this request, but the headers may be useful.

Tells the user agent to reset the document which sent this request.

This response code is used when the Range header is sent from the client to request only part of a resource.

Conveys information about multiple resources, for situations where multiple status codes might be appropriate.

Used inside a <dav:propstat> response element to avoid repeatedly enumerating the internal members.

The server has fulfilled a request for the resource, and the response is a representation of the result.

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

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.

Used for caching purposes. It tells the client that the response has not been modified.

Defined in a previous version of the HTTP specification to indicate that a requested response must be accessed by a proxy.

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 by the Location: HTTP Response header.

The server could not understand the request due to invalid syntax.

The client must authenticate itself to get the requested response.

This response code is reserved for future use. The initial aim was 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 can not find the requested resource. This can also mean that the endpoint is valid but the resource itself does not exist.

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's headers.

This is similar to 401 Unauthorized but authentication is needed to be done by a proxy.

The server would like to shut down this unused connection. It is sent on an idle connection.

Request could not be processed because of conflict in the current state of the resource.

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 and the server requires it.

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 can't be fulfilled.

The expectation given in the request's Expect header could not be met.

The server refuses the attempt to brew coffee with a teapot. 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.

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 be willing after upgrade.

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.

The server has encountered a situation it doesn't know how to handle.

The request method is not supported by the server and cannot be handled.

The server, while working as a gateway to get a response needed to handle the request, got an invalid response.

The server is not ready to handle the request. Common causes are a server that is down for maintenance or overloaded.

The server is acting as a gateway and cannot get a response in time.

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.