Browse and search all HTTP status codes from 1xx to 5xx with detailed descriptions.
Browse, search, and copy all standard HTTP response status codes.
Showing 62 results
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 while the server is preparing a response.
The request has succeeded. The meaning of the success depends on the HTTP method used.
The request has succeeded and a new resource has been created as a result.
The request has been received but not yet acted upon. It is non-committal and intended for asynchronous processing.
The returned metadata is not exactly the same as available from the origin server, but collected from a local or third-party copy.
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 enumerating the internal members of multiple bindings to the same collection repeatedly.
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 applied to the current instance.
The request has more than one possible response. The user agent or user should choose one of them.
The URL of the requested resource has been changed permanently. The new URL is given in the response.
This response code means that the URI of requested resource has been changed temporarily.
The server sent this response to direct the client to get the requested resource at another URI with a GET request.
This is 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 same method that was used in the prior request.
This means that the resource is now permanently located at another URI. This is similar to 301 but the method must not be changed.
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. Semantically 'unauthenticated'.
Reserved for future use. The original intention was that this code might be used as part of some form of digital cash or micropayment scheme.
The client does not have access rights to the content. Unlike 401, the client's identity is known to the server.
The server cannot find the requested resource. The URL is not recognized. This is the most well-known HTTP status code.
The request method is known by the server but is not supported by the target resource.
The server cannot find any content that conforms to the criteria given by the user agent.
This is similar to 401 but authentication is needed to be done by a proxy.
This response is sent on an idle connection by some servers. It means the server decided to close the connection rather than wait.
This response is sent when a request conflicts with the current state of the server.
This response is sent when 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 server might close the connection or return a Retry-After header field.
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, so the server is rejecting the request.
The range specified by the Range header field in the request cannot be fulfilled. It's possible that the range is outside the size of the target data.
This response code means 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 error is a reference to Hyper Text Coffee Pot Control Protocol.
The request was directed at a server that is not able to produce a response. This can be sent by a server not configured to produce responses for the combination of scheme and authority.
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 but might be willing to do so after the client upgrades to a different protocol.
The origin server requires the request to be conditional. This response is intended to prevent the 'lost update' problem.
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, 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 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 that is 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 chosen variant resource is configured to engage in transparent content negotiation itself.
The method could not be performed on the resource because the server is unable to store the representation needed to successfully 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.
Indicates that the client needs to authenticate to gain network access.
