HTTP cheatsheet

HTTP: Status codes

15 common HTTP tasks.

200 OK

The request succeeded and the response has a body.

HTTP/1.1 200 OK

A resource was created. Send its URL in a Location header.

HTTP/1.1 201 Created
Location: /users/43

The request succeeded and there is nothing to return, common for DELETE and PUT.

HTTP/1.1 204 No Content

The resource has moved for good. 308 keeps the request method; browsers may change POST to GET on 301.

HTTP/1.1 301 Moved Permanently
Location: https://example.com/new

The resource is temporarily elsewhere. 307 keeps the request method.

HTTP/1.1 302 Found
Location: /login

The cached copy is still valid, so no body is sent. It answers a conditional request.

HTTP/1.1 304 Not Modified

The request is malformed or invalid, for example bad JSON or a failed validation.

HTTP/1.1 400 Bad Request

Authentication is missing or invalid. Despite the name, it means unauthenticated.

HTTP/1.1 401 Unauthorized
WWW-Authenticate: Bearer

The server knows who you are but you are not allowed to do this.

HTTP/1.1 403 Forbidden

No resource exists at this URL.

HTTP/1.1 404 Not Found

The request conflicts with the current state, such as a duplicate or an edit conflict.

HTTP/1.1 409 Conflict

The request is well-formed but its content failed validation. Many APIs use it for field errors.

HTTP/1.1 422 Unprocessable Content

The client is rate limited. Check Retry-After for when to try again.

HTTP/1.1 429 Too Many Requests
Retry-After: 30

The server hit an unexpected error. It is the server's fault, not the client's.

HTTP/1.1 500 Internal Server Error

502: a gateway got a bad reply from upstream. 503: the service is unavailable or overloaded. 504: the gateway timed out waiting for upstream.

HTTP/1.1 503 Service Unavailable
Retry-After: 120