HTTP/ 49 CODES

HTTP Status Codes

Every HTTP status code on its own page. Each entry covers what the code means, when servers should return it, common causes (for errors), how to fix them, a real curl example, related codes, and a small FAQ. 49 codes documented. Search by number or keyword.

SourceRFC 9110 + extension RFCs

One-pagecheat sheet

Curlcheat sheet

1XX INFORMATIONAL/ REQUEST RECEIVED AND PROCESSING CONTINUES

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

Switching Protocols

The server is switching protocols as requested by the client, typically upgrading from HTTP/1.1 to WebSocket.

The server hints at resources the client can preload while the final response is still being prepared.

2XX SUCCESS/ REQUEST WAS SUCCESSFULLY RECEIVED, UNDERSTOOD, AND ACCEPTED

The request succeeded. The response body contains whatever the request was for.

The request succeeded and a new resource was created as a result.

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

The request succeeded and there is intentionally no response body.

Partial Content

The server is delivering only part of the resource, in response to a Range request from the client.

The response contains a result for multiple sub-operations, each with its own status.

3XX REDIRECTION/ FURTHER ACTION MUST BE TAKEN TO COMPLETE THE REQUEST

Moved Permanently

The resource has permanently moved to a new URL given in the Location header.

The resource is temporarily at a different URL. Use the new URL for this request only.

The response to your request can be found at a different URL, and you should fetch it with GET.

The cached version of the resource is still valid; no body is sent.

Temporary Redirect

The resource is temporarily at a different URL. Use the same HTTP method to access it.

Permanent Redirect

The resource has permanently moved and the same HTTP method must be used at the new URL.

4XX CLIENT ERROR/ THE REQUEST CONTAINS BAD SYNTAX OR CANNOT BE FULFILLED

The server cannot process the request because the client sent something invalid.

The request requires authentication that was not provided or was invalid.

Payment Required

Reserved for future use; in practice, used by some APIs to signal the caller has run out of credits.

The server understood the request and knows who you are, but refuses to authorize it.

The server cannot find the requested resource.

Method Not Allowed

The HTTP method is not supported for this resource.

The server cannot produce a response matching the client's Accept headers.

Request Timeout

The server gave up waiting for the client to finish sending the request.

The request conflicts with the current state of the resource.

The resource is permanently gone and will not return.

Length Required

The request lacks a Content-Length header that the server requires.

Precondition Failed

A precondition header on the request did not match the server's state.

Content Too Large

The request body exceeds the server's size limit.

The URL is longer than the server is willing to interpret.

Unsupported Media Type

The server cannot parse the Content-Type of the request body.

Range Not Satisfiable

The requested byte range is outside the resource's actual size.

The server is a teapot and refuses to brew coffee.

Unprocessable Content

The request is well-formed but contains semantically invalid data.

The resource is locked and cannot be modified right now.

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

Upgrade Required

The client must upgrade to a different protocol to continue.

Precondition Required

The server requires the request to be conditional.

Too Many Requests

The client has sent too many requests in too short a time and is being rate-limited.

Request Header Fields Too Large

The request headers, in total or individually, exceed the server's limit.

Unavailable For Legal Reasons

The resource is blocked due to a legal demand.

5XX SERVER ERROR/ THE SERVER FAILED TO FULFILL AN APPARENTLY VALID REQUEST

Internal Server Error

The server hit an unhandled error while processing the request.

Not Implemented

The server does not support the request method or feature.

A gateway or proxy got an invalid response from an upstream server.

Service Unavailable

The server is temporarily unable to handle the request, usually due to overload or maintenance.

Gateway Timeout

A gateway or proxy did not receive a response from an upstream server in time.

HTTP Version Not Supported

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

Insufficient Storage

The server cannot store the data needed to complete the request.

The server detected an infinite loop while processing the request.

Network Authentication Required

The client must authenticate to the network (captive portal) before accessing the resource.

No matching codes found.