Browse and search through all HTTP status codes with their meanings and descriptions.
The server has received the request headers and the client should proceed to send the request body.
The server is switching protocols according to the Upgrade header sent by the client.
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.
Standard response for successful HTTP requests.
The request has been fulfilled, resulting in the creation of a new resource.
The request has been accepted for processing, but the processing has not been completed.
The server is a transforming proxy that received a 200 OK from its origin.
The server successfully processed the request but is not returning any content.
The server successfully processed the request, asks that the client reset its document view.
The server is delivering only part of the resource due to a range header sent by the client.
The requested resource has multiple choices, each with different qualities.
The requested resource has been permanently moved to a new URL.
The requested resource temporarily resides under a different URL.
The response to the request can be found under a different URL.
The resource has not been modified since the version specified by the request headers.
The requested resource has been permanently moved to another URL.
The server cannot or will not process the request due to an apparent client error.
Authentication is required and has failed or has not been provided.
Reserved for future use. Originally intended for digital payment systems.
The request was valid, but the server is refusing action. The user might not have the necessary permissions.
The requested resource could not be found on the server.
The request method is not supported for the requested resource.
The requested resource is capable of generating only content not acceptable according to the Accept headers sent.
Authentication with the proxy is required before serving the request.
The server timed out waiting for the request.
The request could not be processed because of conflict in the current state of the resource.
The requested resource is no longer available and will not be available again.
The request did not specify the length of its content, which is required by the resource.
The server does not meet one of the preconditions that the requester put on the request.
The request is larger than the server is willing or able to process.
The URI provided was too long for the server to process.
The request entity has a media type which the server or resource does not support.
The client has asked for a portion of the file, but the server cannot supply that portion.
The server cannot meet the requirements of the Expect request-header field.
The server refuses to brew coffee because it is a teapot. (April Fools joke from 1998)
The request was well-formed but was unable to be followed due to semantic errors.
The user has sent too many requests in a given amount of time.
The server encountered an unexpected condition that prevented it from fulfilling the request.
The server does not support the functionality required to fulfill the request.
The server was acting as a gateway or proxy and received an invalid response from the upstream server.
The server is currently unable to handle the request due to temporary overloading or maintenance.
The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.
The server does not support the HTTP protocol version used in the request.
The server has an internal configuration error: the chosen variant resource is configured to engage in transparent content negotiation itself.
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.