HTTP Status Codes 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 (e.g. WebSocket handshake).

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 (e.g. Link headers for preload).

Standard response for successful HTTP requests. The actual response will depend on the request method used.

The request has been fulfilled, resulting in the creation of a new resource (e.g. POST request).

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

The server successfully processed the request and is not returning any content (common for DELETE/PUT).

The server is delivering only part of the resource due to a Range header sent by the client (video streaming).

This and all future requests should be directed to the given URI. Search engines transfer page rank.

Tells the client to look at another URL, but future requests should still use the original URI.

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

The request should be repeated with another URI; however, future requests should still use the original URI (preserves method).

The request and all future requests should be repeated using another URI, preserving the request method.

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

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

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

The requested resource could not be found on this server but may be available in the future.

A request method is not supported for the requested resource (e.g. GET on a form that requires POST).

The server timed out waiting for the request from the client.

Indicates that the request could not be processed because of conflict in the current state of the resource (e.g. duplicate email).

Indicates that the resource requested is no longer available and will not be available again.

The request is larger than the server is willing or able to process (e.g. file upload limit exceeded).

The request entity has a media type which the server or resource does not support (e.g. invalid Content-Type).

The request was well-formed but was unable to be followed due to semantic errors (validation failed).

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

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

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

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

The server is currently unavailable (because it is overloaded or down for maintenance).

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