Search all HTTP status codes from 1xx to 5xx. See what each response code means, with a direct link to the RFC section that defines it.
Updated
The server has received the request headers, and that the client should proceed to send the request body
The requester has asked the server to switch protocols and the server is acknowledging that it will do so
Headers: Upgrade
The server has received the request and is still processing it, so no response is available yet (WebDAV)
The server sends preliminary headers, usually Link headers, so the client can start preloading resources before the final response
Headers: Link
The request has been fulfilled and resulted in a new resource being created
Headers: Location
The request has been accepted for processing, but the processing has not been completed
The server successfully processed the request, but is returning information that may be from another source
The server successfully processed the request, but is not returning any content
The server successfully processed the request, but is not returning any content. Unlike a 204 response, this response requires that the requester reset the document view
The server is delivering only part of the resource (byte serving) due to a range header sent by the client
Headers: Content-Range
The response body holds separate status codes for multiple independent operations (WebDAV)
The members of a binding were already listed in an earlier part of this multistatus response, so they are not repeated (WebDAV)
The server fulfilled a GET request, and the response is the result of instance manipulations applied to the current instance
Indicates multiple options for the resource that the client may follow
This and all future requests should be directed to the given URI
Headers: Location
Clients may change a POST to a GET when they follow a 301. Use 308 to keep the request method.
The target resource resides temporarily under a different URI
Headers: Location
Clients may change a POST to a GET when they follow a 302. Use 307 to keep the request method.
The server is redirecting to a different URI which accesses the same resource
Headers: Location
There is no need to retransmit the resource, since the client still has a previously-downloaded copy
The requested resource must be accessed through the proxy given in the response. Deprecated for security reasons
Used in an earlier draft of HTTP/1.1 for Switch Proxy. The code is reserved and no longer used
The target resource resides temporarily under a different URI, and the client must not change the request method when it follows the redirect
Headers: Location
Like 302, but the client must keep the request method and body.
The target resource has a new permanent URI, and the client must not change the request method when it follows the redirect
Headers: Location
Like 301, but the client must keep the request method and body.
The request could not be understood by the server due to malformed syntax
Use 400 for malformed syntax. Use 422 when the syntax is valid but the content fails validation.
Authentication is required and has failed or has not yet been provided
Headers: WWW-Authenticate
Use 401 when the client is not authenticated. Use 403 when the client is authenticated but has no permission.
The 402 (Payment Required) status code is reserved for future use
The server understood the request but refuses to authorize it
Use 403 when the client is authenticated but has no permission. Use 401 when the client is not authenticated.
The requested resource could not be found but may be available again in the future
Use 410 instead when you know the resource was removed on purpose and will not come back.
A request was made of a resource using a request method not supported by that resource
Headers: Allow
The requested resource is only capable of generating content not acceptable according to the Accept headers sent in the request
The client must first authenticate itself with the proxy
Headers: Proxy-Authenticate
The request could not be processed because of conflict in the request
The resource requested is no longer available and will not be available again
Use 404 instead when you do not know whether the removal is permanent.
The request did not specify the length of its content, which is required by the requested 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 (byte serving), but the server cannot supply that portion
Headers: Content-Range
The server cannot meet the requirements of the Expect request-header field
Reserved. Originally an April Fools joke in RFC 2324 (HTCPCP), and some servers still return it for requests they refuse to handle
The request was sent to a server that cannot produce a response for this combination of scheme and authority
The server understands the content type and the syntax of the request content is correct, but it was unable to process the contained instructions
Use 422 when the syntax is valid but the content fails validation. Use 400 for malformed syntax.
The source or destination resource of the method is locked (WebDAV)
The method could not be performed because it depended on another action that failed (WebDAV)
The server is unwilling to process a request that might be replayed, such as one sent in TLS early data
The client should switch to a different protocol
Headers: Upgrade
The server requires the request to be conditional, for example with If-Match, to prevent lost updates
The client has sent too many requests in a given amount of time (rate limiting). A Retry-After header may say how long to wait
Headers: Retry-After
The server refuses the request because one header field, or all header fields together, are too large
The server denies access to the resource as a consequence of a legal demand
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, while acting as a gateway or proxy, received an invalid response from an inbound server
The upstream server sent an invalid response. Use 504 when the upstream server did not respond in time.
The server is currently unable to handle the request due to a temporary overload or scheduled maintenance
Headers: Retry-After
The server, while acting as a gateway or proxy, did not receive a timely response from an upstream server
The upstream server did not respond in time. Use 502 when it sent an invalid response.
The server does not support, or refuses to support, the major version of HTTP that was used in the request
The server has an internal configuration error: the chosen variant resource is itself set up to do content negotiation
The server cannot store the representation needed to complete the request (WebDAV)
The server ended the operation because it found an infinite loop while processing a request with Depth: infinity (WebDAV)
Further extensions to the request are required for the server to fulfill it. The defining RFC 2774 is now historic
The client needs to authenticate to gain network access, as with a captive portal on public Wi-Fi
No status codes match your search.
The first digit of a status code is its class. 1xx responses are informational, 2xx mean the request succeeded, 3xx ask the client to go somewhere else, 4xx point to a problem with the request, and 5xx point to a problem on the server.
Link straight to a code with its anchor, for example /http-status-codes.html#404, or use its Copy link button. To share a search, add ?q=, for example ?q=retry-after.