HTTP Status 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. Often used for WebSockets.

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 standard response for successful HTTP requests. The actual response will depend on the request method used (GET, POST, etc.).

How to handle: No action needed. The request succeeded.

The request has been fulfilled, resulting in the creation of a new resource.

How to handle: Often returned by POST requests. Look for a Location header for the new resource URL.

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, but is returning a modified version of the origin's response.

The server successfully processed the request and is not returning any content.

How to handle: Commonly used for DELETE requests or when a client doesn't need to navigate away from the current page.

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. Common for video streaming.

The message body that follows is by default an XML message and can contain a number of separate response codes, depending on how many sub-requests were made.

The members of a DAV binding have already been enumerated in a preceding part of the (multistatus) response, and are not being included again.

The server has fulfilled a request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance.

Indicates multiple options for the resource from which the client may choose (via agent-driven content negotiation).

This and all future requests should be directed to the given URI.

How to handle: Update any bookmarks or links to use the new URL. Search engines will transfer SEO ranking to the new destination.

Tells the client to look at (browse to) another URL. The HTTP method may change to GET.

How to handle: Often used for temporary redirects. If it is permanent, use 301 instead.

The response to the request can be found under another URI using the GET method.

Indicates that the resource has not been modified since the version specified by the request headers If-Modified-Since or If-None-Match.

How to handle: The client should use its cached version of the resource to save bandwidth.

The requested resource is available only through a proxy, the address for which is provided in the response.

In this case, the request should be repeated with another URI; however, future requests should still use the original URI. The HTTP method must not change.

The request and all future requests should be repeated using another URI. 308 parallels the behavior of 301, but does not allow the HTTP method to change.

How to handle: Use this instead of 301 if you need to guarantee that POST requests remain POST requests after the redirect.

The server cannot or will not process the request due to an apparent client error (e.g., malformed request syntax, size too large, invalid request message framing).

How to handle: Check the syntax of your request, verify API parameters, and ensure JSON bodies are properly formatted.

Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided.

How to handle: Ensure you are sending the correct Authentication headers (e.g., Bearer tokens, API keys) with your request.

Reserved for future use. Originally intended to be used as part of a digital cash or micropayment scheme.

The request contained valid data and was understood by the server, but the server is refusing action.

How to handle: This usually means you are authenticated, but you do not have permission/authorization to access this specific resource.

The requested resource could not be found but may be available in the future. Subsequent requests by the client are permissible.

How to handle: Verify the URL path is correct. If this is an API, ensure the resource ID exists.

A request method is not supported for the requested resource; for example, a GET request on a form that requires data to be presented via POST.

How to handle: Check which HTTP method (GET, POST, PUT, DELETE) the endpoint actually supports.

The requested resource is capable of generating only content not acceptable according to the Accept headers sent in the request.

The client must first authenticate itself with the proxy.

The server timed out waiting for the request.

Indicates that the request could not be processed because of conflict in the current state of the resource.

How to handle: Commonly occurs in POST/PUT requests when creating a duplicate record or updating a stale resource (e.g., edit collisions).

Indicates that the resource requested is no longer available and will not be available again. Better than 404 for SEO when a page is intentionally deleted.

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 header fields.

The request is larger than the server is willing or able to process.

The URI provided was too long for the server to process. Often the result of too much data being encoded as a query-string of a GET request.

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.

An April Fools' joke defined in RFC 2324. Indicates the server refuses to brew coffee because it is, permanently, a teapot.

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.

How to handle: Usually means your JSON was valid, but a required field was missing or a validation rule failed (e.g. invalid email format).

The resource that is being accessed is locked.

The request failed because it depended on another request and that request failed.

Indicates that the server is unwilling to risk processing a request that might be replayed.

The client should switch to a different protocol such as TLS/1.0, given in the Upgrade header field.

The origin server requires the request to be conditional.

The user has sent too many requests in a given amount of time (rate limiting).

How to handle: Implement exponential backoff in your code. Look for a "Retry-After" header indicating how long to wait before trying again.

The server is unwilling to process the request because either an individual header field, or all the header fields collectively, are too large.

A server operator has received a legal demand to deny access to a resource or to a set of resources that includes the requested resource.

A generic error message, given when an unexpected condition was encountered and no more specific message is suitable.

How to handle: Check server logs for stack traces. This is usually caused by unhandled exceptions, syntax errors, or database connection failures.

The server either does not recognize the request method, or it lacks the ability to fulfill the request.

The server was acting as a gateway or proxy and received an invalid response from the upstream server.

How to handle: Often occurs in reverse proxy setups (Nginx, HAProxy) when the backend application server crashes or restarts.

The server cannot handle the request (because it is overloaded or down for maintenance). Generally, this is a temporary state.

How to handle: If you are the administrator, scale up resources or wait for maintenance to finish.

The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.

How to handle: Occurs when a backend process takes too long (e.g. slow database query). Increase proxy timeouts or optimize the backend process.

The server does not support the HTTP protocol version used in the request.

Transparent content negotiation for the request results in a circular reference.

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. Intended for use by intercepting proxies used to control access to the network.