RFC 9110
Continue
The server has received the request headers and the client should proceed to send the request body.
Default Caching:Not Cacheable
RFC 9110
Switching Protocols
The requester has asked the server to switch protocols (e.g. HTTP to WebSocket).
Default Caching:Not Cacheable
RFC 9110
OK
Standard response for successful HTTP requests.
Default Caching:Cacheable
RFC 9110
Created
The request has been fulfilled, resulting in the creation of a new resource.
Default Caching:Cacheable
RFC 9110
Accepted
The request has been accepted for processing, but processing has not completed.
Default Caching:Not Cacheable
RFC 9110
No Content
The server successfully processed the request, but is not returning any content.
Default Caching:Cacheable
RFC 9110
Partial Content
The server is delivering only part of the resource due to a Range header sent by the client.
Default Caching:Cacheable
RFC 9110
Moved Permanently
This and all future requests should be directed to the given URI in the Location header.
Default Caching:Cacheable
RFC 9110
Found (Temporary Redirect)
Tells the client to look at another URL temporarily.
Default Caching:Not Cacheable
RFC 9110
Not Modified
Indicates that the resource has not been modified since the version specified by the request headers.
Default Caching:Cacheable
RFC 9110
Temporary Redirect
The request should be repeated with another URI, preserving the HTTP method (e.g. POST remains POST).
Default Caching:Not Cacheable
RFC 9110
Permanent Redirect
The request and all future requests should be repeated using another URI, preserving the HTTP method.
Default Caching:Cacheable
RFC 9110
Bad Request
The server cannot process the request due to a client error (e.g. malformed syntax, invalid request framing).
Default Caching:Not Cacheable
RFC 9110
Unauthorized
Authentication is required and has failed or has not yet been provided.
Default Caching:Not Cacheable
RFC 9110
Forbidden
The request contained valid data and was understood by the server, but the server refuses action.
Default Caching:Not Cacheable
RFC 9110
Not Found
The requested resource could not be found but may be available in the future.
Default Caching:Cacheable
RFC 9110
Method Not Allowed
A request method is not supported for the requested resource (e.g. GET on a POST-only endpoint).
Default Caching:Not Cacheable
RFC 9110
Request Timeout
The server timed out waiting for the request.
Default Caching:Not Cacheable
RFC 9110
Conflict
Indicates that the request could not be processed because of conflict in the current state of the resource.
Default Caching:Not Cacheable
RFC 9110
Gone
Indicates that the resource requested is no longer available and will not be available again.
Default Caching:Cacheable
RFC 9110
Payload Too Large
The request is larger than the server is willing or able to process.
Default Caching:Not Cacheable
RFC 9110
Unprocessable Content
The request was well-formed but was unable to be followed due to semantic errors.
Default Caching:Not Cacheable
RFC 6585
Too Many Requests
The user has sent too many requests in a given amount of time (rate limiting).
Default Caching:Not Cacheable
RFC 9110
Internal Server Error
A generic error message, given when an unexpected condition was encountered.
Default Caching:Not Cacheable
RFC 9110
Not Implemented
The server either does not recognize the request method, or lacks the ability to fulfill it.
Default Caching:Not Cacheable
RFC 9110
Bad Gateway
The server, while acting as a gateway or proxy, received an invalid response from the inbound server.
Default Caching:Not Cacheable
RFC 9110
Service Unavailable
The server cannot handle the request (because it is overloaded or down for maintenance).
Default Caching:Not Cacheable
RFC 9110
Gateway Timeout
The server, while acting as a gateway or proxy, did not receive a timely response from upstream.
Default Caching:Not Cacheable