HTTP Status Codes

100 Continue

Waiting for the client to emit the body of the request.

101 Switching Protocols

The server has agreed to change protocol.

102 Processing

The server is processing the request, but no response is available yet. For WebDav.

103 Early Hints

The server returns some response headers before final HTTP message.

200 OK

Standard response for successful HTTP requests.

201 Created

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

202 Accepted

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

203 Non-Authoritative Information

The server is a transforming proxy that received a 200 OK from its origin.

204 No Content

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

205 Reset Content

The server successfully processed the request, asks that the requester reset its document view.

206 Partial Content

The server is delivering only part of the resource due to a range header sent by the client.

207 Multi-Status

The message body contains multiple status codes for separate operations. For WebDav.

208 Already Reported

The members of a DAV binding have already been enumerated. For WebDav.

226 IM Used

The server has fulfilled a request for the resource with instance-manipulations applied.

300 Multiple Choices

Indicates multiple options for the resource from which the client may choose.

301 Moved Permanently

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

302 Found

Tells the client to look at another URL. Previously "Moved Temporarily".

303 See Other

The response can be found under another URI using the GET method.

304 Not Modified

Indicates that the resource has not been modified since the version specified by the request headers.

305 Use Proxy

The requested resource is available only through a proxy. Deprecated.

307 Temporary Redirect

The request should be repeated with another URI, but future requests should still use the original URI.

308 Permanent Redirect

This and all future requests should be directed to the given URI. Does not allow method change.

400 Bad Request

The server cannot process the request due to a client error (e.g., malformed request syntax).

401 Unauthorized

Authentication is required and has failed or has not yet been provided.

402 Payment Required

Reserved for future use. Sometimes used for digital payment systems.

403 Forbidden

The client does not have access rights to the content; the server is refusing to give the resource.

404 Not Found

The server cannot find the requested resource. The most well-known HTTP status code.

405 Method Not Allowed

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

406 Not Acceptable

The target resource does not have a current representation acceptable to the user agent.

407 Proxy Authentication Required

The client must first authenticate itself with the proxy.

408 Request Timeout

The server timed out waiting for the request.

409 Conflict

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

410 Gone

The resource requested was previously in use but is no longer available and will not be available again.

411 Length Required

The request did not specify the length of its content, which is required by the resource.

412 Precondition Failed

The server does not meet one of the preconditions specified in the request headers.

413 Content Too Large

The request is larger than the server is willing or able to process.

414 URI Too Long

The URI provided was too long for the server to process.

415 Unsupported Media Type

The request entity has a media type which the server does not support.

416 Range Not Satisfiable

The client has asked for a portion of the file, but the server cannot supply that portion.

417 Expectation Failed

The server cannot meet the requirements of the Expect request-header field.

418 I'm a Teapot

The server refuses the attempt to brew coffee with a teapot. An April Fools' joke (RFC 2324).

421 Misdirected Request

The request was directed at a server that is not able to produce a response.

422 Unprocessable Content

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

423 Locked

The resource that is being accessed is locked. For WebDav.

424 Failed Dependency

The request failed because it depended on another request and that request failed. For WebDav.

425 Too Early

The server is unwilling to risk processing a request that might be replayed.

426 Upgrade Required

The client should switch to a different protocol such as TLS/1.3.

428 Precondition Required

The origin server requires the request to be conditional.

429 Too Many Requests

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

431 Request Header Fields Too Large

The server is unwilling to process the request because its header fields are too large.

451 Unavailable For Legal Reasons

The user agent requested a resource that cannot legally be provided.

500 Internal Server Error

A generic error message when an unexpected condition was encountered.

501 Not Implemented

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

502 Bad Gateway

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

503 Service Unavailable

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

504 Gateway Timeout

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

505 HTTP Version Not Supported

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

506 Variant Also Negotiates

Transparent content negotiation for the request results in a circular reference.

507 Insufficient Storage

The server is unable to store the representation needed to complete the request. For WebDav.

508 Loop Detected

The server detected an infinite loop while processing the request. For WebDav.

510 Not Extended

Further extensions to the request are required for the server to fulfil it.

511 Network Authentication Required

The client needs to authenticate to gain network access (e.g., captive portal).