HTTP Status Code Reference

Continue

The server has received the request headers and the client should proceed to send the request body.

Switching Protocols

The server agrees to switch protocols as requested by the client, e.g. upgrading to WebSocket.

Processing

The server has received and is processing the request, but no response is available yet.

OK

The request succeeded. The meaning depends on the HTTP method: GET returns the resource, POST returns the result.

Created

The request succeeded and a new resource was created. Typically returned in response to POST or PUT.

Accepted

The request has been accepted for processing, but the processing has not been completed.

No Content

The server successfully processed the request but is not returning any content. Common for DELETE.

Partial Content

The server is delivering only part of the resource due to a range request from the client.

Moved Permanently

The URL of the requested resource has changed permanently. Future requests should use the new URL.

Found

The target resource resides temporarily under a different URI. The client should continue using the original.

Not Modified

The client's cached version is up-to-date. The server is telling the client to use the cached copy.

Temporary Redirect

The target resource resides temporarily under a different URI. The request method must not change.

Permanent Redirect

The resource is now permanently located at another URI. The request method must not change.

Bad Request

The server cannot process the request due to a client error (malformed syntax, invalid framing, etc.).

Unauthorized

The client must authenticate itself to get the requested response. The client is not authenticated.

Forbidden

The client does not have access rights to the content. Unlike 401, the server knows who the client is.

Not Found

The server cannot find the requested resource. The URL is not recognized or the resource doesn't exist.

Method Not Allowed

The request method is known by the server but is not supported by the target resource.

Request Timeout

The server would like to shut down this unused connection. It is sent on an idle connection.

Conflict

The request conflicts with the current state of the server, e.g. a version conflict on a PUT request.

Gone

The requested content has been permanently deleted from the server, with no forwarding address.

Content Too Large

The request body is larger than limits defined by server. The server may close the connection.

Unprocessable Content

The request is well-formed but was unable to be followed due to semantic errors.

Too Many Requests

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

Internal Server Error

The server encountered an unexpected condition that prevented it from fulfilling the request.

Not Implemented

The server does not support the functionality required to fulfill the request.

Bad Gateway

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

Service Unavailable

The server is not ready to handle the request. Common causes are server overload or maintenance.

Gateway Timeout

The server is acting as a gateway and the upstream server did not respond in time.

HTTP Version Not Supported

The HTTP version used in the request is not supported by the server.