100 | Continue | The server has received the request headers and the client should proceed to send the request body. | Informational | RFC9110, Section 15.2.1 |
101 | Switching Protocols | The requester has asked the server to switch protocols and the server has agreed to do so. | Informational | RFC9110, Section 15.2.2 |
102 | Processing | The server is processing the request but has not yet responded. | Informational | RFC2518 |
103 | Early Hints | Used to return some response headers prior to the final HTTP message. | Informational | RFC8297 |
104 | Upload Resumption Supported | Indicates that the server supports resumption of the upload. | Informational | draft-ietf-httpbis-resumable-upload-05 |
200 | OK | The request has succeeded. | Success | RFC9110, Section 15.3.1 |
201 | Created | The request has succeeded and a new resource has been created. | Success | RFC9110, Section 15.3.2 |
202 | Accepted | The request has been accepted for processing, but the processing has not been completed. | Success | RFC9110, Section 15.3.3 |
203 | Non-Authoritative Information | The request was successful but the response may be from a third-party source or local copy. | Success | RFC9110, Section 15.3.4 |
204 | No Content | The request has been successfully processed, but there is no content to return. | Success | RFC9110, Section 15.3.5 |
205 | Reset Content | The request has been successfully processed, and the client should reset the document view. | Success | RFC9110, Section 15.3.6 |
206 | Partial Content | The server is delivering only part of the resource due to a range header sent by the client. | Success | RFC9110, Section 15.3.7 |
207 | Multi-Status | Provides status for multiple independent operations. | Success | RFC4918 |
208 | Already Reported | Used inside a DAV: propstat response element to avoid enumerating the internal members of multiple bindings to the same collection repeatedly. | Success | RFC5842 |
226 | IM Used | The server has fulfilled a request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance. | Success | RFC3229 |
300 | Multiple Choices | The request has more than one possible response. | Redirection | RFC9110, Section 15.4.1 |
301 | Moved Permanently | The resource has moved permanently and is now at a new URI. | Redirection | RFC9110, Section 15.4.2 |
302 | Found | The resource has moved temporarily to a different URI. | Redirection | RFC9110, Section 15.4.3 |
303 | See Other | The response to the request can be found under a different URI and should be retrieved using a GET method. | Redirection | RFC9110, Section 15.4.4 |
304 | Not Modified | The resource has not been modified since the version specified by the request headers. | Redirection | RFC9110, Section 15.4.5 |
305 | Use Proxy | The requested resource must be accessed through the proxy given by the Location field. | Redirection | RFC9110, Section 15.4.6 |
306 | (Unused) | No longer used. Originally meant to indicate that subsequent requests should use the specified proxy. | Redirection | RFC9110, Section 15.4.7 |
307 | Temporary Redirect | The request should be repeated with another URI but future requests can still use the original URI. | Redirection | RFC9110, Section 15.4.8 |
308 | Permanent Redirect | The request and all future requests should be repeated using another URI. | Redirection | RFC9110, Section 15.4.9 |
400 | Bad Request | The server cannot or will not process the request due to an apparent client error. | Client Error | RFC9110, Section 15.5.1 |
401 | Unauthorized | The request requires user authentication. | Client Error | RFC9110, Section 15.5.2 |
402 | Payment Required | Reserved for future use. | Client Error | RFC9110, Section 15.5.3 |
403 | Forbidden | The server understood the request but refuses to authorize it. | Client Error | RFC9110, Section 15.5.4 |
404 | Not Found | The requested resource could not be found but may be available in the future. | Client Error | RFC9110, Section 15.5.5 |
405 | Method Not Allowed | A request method is not supported for the requested resource. | Client Error | RFC9110, Section 15.5.6 |
406 | Not Acceptable | The requested resource is capable of generating only content not acceptable according to the Accept headers sent in the request. | Client Error | RFC9110, Section 15.5.7 |
407 | Proxy Authentication Required | The client must first authenticate itself with the proxy. | Client Error | RFC9110, Section 15.5.8 |
408 | Request Timeout | The server timed out waiting for the request. | Client Error | RFC9110, Section 15.5.9 |
409 | Conflict | The request could not be completed due to a conflict with the current state of the target resource. | Client Error | RFC9110, Section 15.5.10 |
410 | Gone | The requested resource is no longer available and will not be available again. | Client Error | RFC9110, Section 15.5.11 |
411 | Length Required | The request did not specify the length of its content, which is required by the requested resource. | Client Error | RFC9110, Section 15.5.12 |
412 | Precondition Failed | The server does not meet one of the preconditions specified in the request. | Client Error | RFC9110, Section 15.5.13 |
413 | Content Too Large | The request entity is larger than limits defined by the server. | Client Error | RFC9110, Section 15.5.14 |
414 | URI Too Long | The URI provided was too long for the server to process. | Client Error | RFC9110, Section 15.5.15 |
415 | Unsupported Media Type | The request entity has a media type which the server or resource does not support. | Client Error | RFC9110, Section 15.5.16 |
416 | Range Not Satisfiable | The client has asked for a portion of the file, but the server cannot supply that portion. | Client Error | RFC9110, Section 15.5.17 |
417 | Expectation Failed | The server cannot meet the requirements of the Expect request-header field. | Client Error | RFC9110, Section 15.5.18 |
418 | (Unused) | The server refuses the attempt to brew coffee with a teapot. | Client Error | RFC9110, Section 15.5.19 |
421 | Misdirected Request | The request was directed at a server that is not able to produce a response. | Client Error | RFC9110, Section 15.5.20 |
422 | Unprocessable Content | The request was well-formed but was unable to be followed due to semantic errors. | Client Error | RFC9110, Section 15.5.21 |
423 | Locked | The resource that is being accessed is locked. | Client Error | RFC4918 |
424 | Failed Dependency | The request failed because it depended on another request and that request failed. | Client Error | RFC4918 |
425 | Too Early | Indicates that the server is unwilling to risk processing a request that might be replayed. | Client Error | RFC8470 |
426 | Upgrade Required | The client should switch to a different protocol such as TLS/1.0. | Client Error | RFC9110, Section 15.5.22 |
428 | Precondition Required | The origin server requires the request to be conditional. | Client Error | RFC6585 |
429 | Too Many Requests | The user has sent too many requests in a given amount of time. | Client Error | RFC6585 |
431 | Request Header Fields Too Large | The server is unwilling to process the request because its header fields are too large. | Client Error | RFC6585 |
451 | Unavailable For Legal Reasons | The server is denying access to the resource as a consequence of a legal demand. | Client Error | RFC7725 |
500 | Internal Server Error | A generic error message, given when an unexpected condition was encountered. | Server Error | RFC9110, Section 15.6.1 |
501 | Not Implemented | The server either does not recognize the request method, or it lacks the ability to fulfill the request. | Server Error | RFC9110, Section 15.6.2 |
502 | Bad Gateway | The server was acting as a gateway or proxy and received an invalid response from the upstream server. | Server Error | RFC9110, Section 15.6.3 |
503 | Service Unavailable | The server is currently unable to handle the request due to a temporary overload or maintenance of the server. | Server Error | RFC9110, Section 15.6.4 |
504 | Gateway Timeout | The server was acting as a gateway or proxy and did not receive a timely response from the upstream server. | Server Error | RFC9110, Section 15.6.5 |
505 | HTTP Version Not Supported | The server does not support the HTTP protocol version used in the request. | Server Error | RFC9110, Section 15.6.6 |
506 | Variant Also Negotiates | Transparent content negotiation for the request results in a circular reference. | Server Error | RFC2295 |
507 | Insufficient Storage | The server is unable to store the representation needed to complete the request. | Server Error | RFC4918 |
508 | Loop Detected | The server detected an infinite loop while processing the request. | Server Error | RFC5842 |
510 | Not Extended | Further extensions to the request are required for the server to fulfill it. | Server Error | RFC2774 |
511 | Network Authentication Required | The client needs to authenticate to gain network access. | Server Error | RFC6585 |
