http
HTTP Status Codes
Status codes returned by HTTP servers, as defined in RFC 9110 and related specifications.
61 codes
1xx Informational 4 codes
- 100 Continue The server has received the request headers. The client should proceed to send the request body.
- 101 Switching Protocols The server is switching protocols as requested by the client, for example upgrading from HTTP/1.1 to WebSocket.
- 102 Processing The server has received and is processing the request, but no response is available yet.
- 103 Early Hints Used to return some response headers before final HTTP message, allowing the client to begin preloading resources.
2xx Success 10 codes
- 200 OK The request succeeded. The meaning of success depends on the HTTP method used.
- 201 Created The request succeeded and a new resource was created. The new resource is returned in the response body or via the Location header.
- 202 Accepted The request has been accepted for processing, but processing has not been completed and may not be acted upon.
- 203 Non-Authoritative Information The request succeeded, but the enclosed payload has been modified by a transforming proxy from the origin server's 200 response.
- 204 No Content The request succeeded and there is no additional content to send in the response body.
- 205 Reset Content The request succeeded. The client should reset the document view that caused this request to be sent.
- 206 Partial Content The server is delivering only part of the resource due to a Range header sent by the client.
- 207 Multi-Status Conveys information about multiple resources, for situations where multiple status codes might be appropriate.
- 208 Already Reported The members of a DAV binding have already been enumerated in a preceding part of the response and are not included again.
- 226 IM Used The server fulfilled a GET request and the response is a representation of the result of one or more instance manipulations applied to the current instance.
3xx Redirection 7 codes
- 300 Multiple Choices The request has more than one possible response. The client should choose one of them.
- 301 Moved Permanently The URL of the requested resource has been changed permanently. The new URL is given in the response.
- 302 Found The URI of the requested resource has been changed temporarily. The client should continue to use the original URI.
- 303 See Other The server is redirecting the client to a different resource, indicated by a URI in the Location header, using a GET request.
- 304 Not Modified Indicates the resource has not been modified since the version specified in the request headers. The client can use its cached version.
- 307 Temporary Redirect The requested resource is temporarily located at a different URI. The client must use the same HTTP method for the redirected request.
- 308 Permanent Redirect The resource is permanently located at another URI, given in the Location header. The client must use the same HTTP method for future requests.
4xx Client error 29 codes
- 400 Bad Request The server cannot process the request due to a client error, such as malformed request syntax or invalid request framing.
- 401 Unauthorized The request lacks valid authentication credentials. The client must authenticate itself to get the requested response.
- 402 Payment Required Reserved for future use. Originally intended for digital payment schemes; now occasionally used by APIs to indicate quota exhaustion.
- 403 Forbidden The client does not have permission to access the requested resource. Unlike 401, authentication will not change the outcome.
- 404 Not Found The server cannot find the requested resource. The URL may be wrong, or the resource may not exist.
- 405 Method Not Allowed The HTTP method used is not supported for the requested resource.
- 406 Not Acceptable The server cannot produce a response matching the criteria specified in the request's Accept headers.
- 407 Proxy Authentication Required The client must authenticate itself with the proxy before this request can be served.
- 408 Request Timeout The server timed out waiting for the request. The client may repeat the request without modifications.
- 409 Conflict The request conflicts with the current state of the server, such as a version conflict on a resource update.
- 410 Gone The requested resource is permanently gone and will not be available again. Unlike 404, this condition is expected to be permanent.
- 411 Length Required The server refuses to accept the request without a defined Content-Length header.
- 412 Precondition Failed The server does not meet one or more preconditions specified in the request headers.
- 413 Content Too Large The request body exceeds the limits defined by the server.
- 414 URI Too Long The URI requested by the client is longer than the server is willing to interpret.
- 415 Unsupported Media Type The media format of the requested data is not supported by the server.
- 416 Range Not Satisfiable The range specified by the Range header in the request cannot be fulfilled; it may be outside the size of the target resource.
- 417 Expectation Failed The expectation indicated by the Expect request header cannot be met by the server.
- 418 I'm a Teapot The server refuses to brew coffee because it is, permanently, a teapot. An April Fools' joke from RFC 2324 that became an informal standard.
- 421 Misdirected Request The request was directed at a server that is not able to produce a response for the requested URI.
- 422 Unprocessable Content The request was well-formed but could not be followed due to semantic errors in the contained instructions.
- 423 Locked The resource being accessed is locked.
- 424 Failed Dependency The request failed because it depended on another request that failed.
- 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, specified in the Upgrade header.
- 428 Precondition Required The origin server requires the request to be conditional, to prevent lost-update problems.
- 429 Too Many Requests The client 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 server is denying access to the resource as a consequence of a legal demand. The code is a reference to Fahrenheit 451.
5xx Server error 11 codes
- 500 Internal Server Error The server encountered an unexpected condition that prevented it from fulfilling the request.
- 501 Not Implemented The server does not support the functionality required to fulfil the request.
- 502 Bad Gateway The server, while acting as a gateway or proxy, received an invalid response from an upstream server.
- 503 Service Unavailable The server is not ready to handle the request, typically due to temporary overload or scheduled maintenance.
- 504 Gateway Timeout The server, while acting as a gateway or proxy, did not receive a timely response from an upstream server.
- 505 HTTP Version Not Supported The HTTP version used in the request is not supported by the server.
- 506 Variant Also Negotiates The server has an internal configuration error: the chosen variant resource is configured to engage in transparent content negotiation itself.
- 507 Insufficient Storage The server is unable to store the representation needed to complete the request.
- 508 Loop Detected The server detected an infinite loop while processing the request.
- 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, typically used by captive portals.