HTTP Status Codes Reference

Initial part of a request has been received and hasn't yet been rejected by the server.

The requester has asked the server to switch protocols (e.g. HTTP to WebSocket).

WebDAV: Server has received and is processing the request, but no response is available yet.

Used to return headers like Link preload before final HTTP message.

Standard response for successful HTTP requests.

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

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

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

The server is delivering only part of the resource (byte serving) due to a Range header.

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

The resource currently resides temporarily under a different URI.

Resource has not been modified since the version specified by request headers (If-Modified-Since / ETag).

Request should be repeated with another URI; request method must NOT be changed.

Request and all future requests should be repeated using another URI without changing method.

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

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 refuses action.

The requested resource could not be found on the server.

Request method is not supported for the requested resource (e.g. GET on a POST-only form).

The server timed out waiting for the request.

Request could not be processed because of conflict in the current state of the resource.

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.

Request entity has a media type which the server or resource does not support.

Request was well-formed but was unable to be followed due to semantic errors.

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

Generic error message when an unexpected condition was encountered on the server.

Server does not recognize request method, or lacks ability to fulfill request.

Server acting as gateway/proxy received an invalid response from inbound server.

The server cannot handle the request (temporarily overloaded or down for maintenance).

Server acting as gateway/proxy did not receive a timely response from upstream server.

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