Complete HTTP status codes reference with descriptions — search 60+ codes from 1xx to 5xx. Free and instant.
61 of 61 codes
The server 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.
The server has received and is processing the request, but no response is available yet.
Used to return some response headers before the final HTTP message, enabling the client to preload resources.
The request has succeeded. The meaning varies by HTTP method: GET returns the resource, POST returns the result of the action.
The request has been fulfilled and a new resource has been created. The new resource URI is returned in the Location header.
The request has been accepted for processing, but the processing has not been completed. Useful for async operations.
The returned metadata is not exactly the same as available from the origin server, but is from a local or third-party copy.
The server successfully processed the request and is not returning any content. Common for DELETE or PUT responses.
The server successfully processed the request, asks that the requester reset its document view, and is not returning any content.
The server is delivering only part of the resource due to a Range header sent by the client. Used for resumable downloads.
The message body is an XML document containing multiple separate response codes. Used by WebDAV.
The members of a DAV binding have already been enumerated in a preceding part of the multistatus response.
The server fulfilled a request using one or more instance manipulations. The body is the result of applying those manipulations.
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.
The URI of requested resource has been changed temporarily. Further changes may be made to the URI in the future.
The server sent this response to direct the client to get the requested resource at another URI with a GET request.
The response has not been modified. The client can use the cached version. Reduces bandwidth usage.
The server sends this response to direct the client to get the requested resource at another URI with the same method used.
The resource is now permanently located at another URI, specified by the Location header. The method must not change.
The server cannot process the request due to a client error such as malformed syntax, invalid request message framing, or deceptive routing.
Authentication is required and has failed or has not been provided. Differs from 403 in that authentication may help.
Reserved for future use. Originally intended for digital payment schemes; now sometimes used by APIs to indicate a quota exceeded.
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. This can mean the URL is wrong, or the resource is unavailable.
The request method is known by the server but is not supported by the target resource (e.g., using DELETE on a read-only resource).
The server cannot produce a response matching the list of acceptable values defined in the request's content negotiation headers.
The client must first authenticate itself with the proxy before making requests.
The server would like to shut down this unused connection. It is sent on an idle connection by the server.
The request conflicts with the current state of the server (e.g., conflicting edits to a resource).
The content has been permanently deleted from the server, with no forwarding address. Clients should remove their caches.
The server refuses to accept the request without a defined Content-Length header.
The client has indicated preconditions in its headers which the server does not meet.
The request body is larger than limits defined by the server. The server may close the connection or return a Retry-After header.
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 the range is outside the size of the data.
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. An April Fools' joke from RFC 2324 that became a de facto standard.
The request was directed at a server that is not able to produce a response. This can be sent by a server that is 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. Common in REST APIs for validation failures.
The resource that is being accessed is locked (WebDAV).
The request failed because it depended on another request and that request failed (WebDAV).
Indicates that the server is unwilling to risk processing a request that might be replayed to prevent replay attacks.
The server refuses to perform the request using the current protocol but might be willing if the client upgrades to a different protocol.
The origin server requires the request to be conditional. Intended to prevent "lost update" problems.
The user has sent too many requests in a given amount of time (rate limiting). May include a Retry-After header.
The server is unwilling to process the request because its header fields are too large. The request may be resubmitted after reducing the size of the request header fields.
The server is denying access to the resource as a consequence of a legal demand (e.g., government censorship or court order).
A generic error indicating an unexpected condition was encountered. Usually means a bug in the server-side code.
The server does not support the functionality required to fulfill the request. Usually means the request method is not recognized.
The server, while acting as a gateway or proxy, received an invalid response from the upstream server.
The server is not ready to handle the request. Common causes are a server that is down for maintenance or is overloaded.
The server, while acting as a gateway or proxy, did not receive a timely response from an upstream server.
The HTTP version used in the request is not supported by the server.
The server has an internal configuration error: transparent content negotiation for the request results in a circular reference.
The method could not be performed on the resource because the server is unable to store the representation needed (WebDAV).
The server detected an infinite loop while processing the request (WebDAV).
Further extensions to the request are required for the server to fulfill it.
The client needs to authenticate to gain network access. Intended for use by intercepting proxies (e.g., captive portals).