HTTP Status Code Reference

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.

WebDAV: 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.

The request succeeded. Response depends on method: GET returns the resource, POST returns result of the action.

The request succeeded and a new resource was created. Typically the response for POST requests.

The request has been received but not yet acted upon. Common in async / batch processing.

The request succeeded but no content is returned. Common for DELETE and PUT responses.

Used to deliver a range of a resource - for resumable downloads and video streaming.

The resource has been moved permanently to a new URL. Search engines will update indexes.

The resource is temporarily at a different URL. Original URL should still be used for future requests.

The cached version is still valid. Used with If-Modified-Since or ETag headers.

Like 302, but the method (POST/PUT) must not change on redirect.

Like 301, but the method must not change on redirect.

The server can't process the request due to a client error (malformed syntax, invalid JSON, missing fields).

Authentication is required and has failed or not been provided. Send an Authorization header.

Reserved for future use. Sometimes used by APIs to indicate quota / billing issues.

The server understood the request but refuses to authorize it. Different from 401 - auth won't help.

The server can't find the requested resource. Check the URL and route definitions.

The HTTP method is not supported for this resource. Check the Allow response header.

The server timed out waiting for the request. Client may retry without modifications.

The request conflicts with current state - commonly a version conflict or duplicate resource.

The resource is permanently gone. Stronger than 404 - signals the removal is intentional.

The request body exceeds the server's size limit. Check nginx/gateway client_max_body_size.

The Content-Type isn't supported. Check the Content-Type header.

An April Fools' joke from RFC 2324. Occasionally used as a placeholder or easter egg.

The request is well-formed but semantically invalid. Very common in JSON APIs for validation errors.

Rate limit exceeded. Check the Retry-After header for how long to wait.

A generic error indicating something went wrong on the server. Check server logs.

The server doesn't support the functionality required to fulfill the request.

The server, acting as a gateway, received an invalid response from an upstream server.

The server is not ready to handle the request - commonly during maintenance or overload.

The server, acting as a gateway, did not get a response in time from the upstream server.

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