HTTP Status Codes
Searchable reference of HTTP status codes and their meanings.
Related
Searchable reference of HTTP status codes and their meanings.
Related
Search for a tool or run a command
The server has received the request headers and the client should proceed to send the body.
The requester has asked the server to switch protocols.
Used to return some response headers before final HTTP message.
Standard response for successful HTTP requests.
The request has been fulfilled and a new resource created.
The request has been accepted for processing, but not completed.
The server successfully processed the request and is not returning content.
The server is delivering only part of the resource (range request).
This and all future requests should be directed to the given URI.
Tells the client to look at another URL (temporary redirect).
The response can be found under another URI using GET.
The resource has not been modified since the version specified by request headers.
Repeat the request to another URI with the same method.
The request and all future requests should be repeated using another URI.
The server cannot process the request due to a client error.
Authentication is required and has failed or not been provided.
Reserved for future use; sometimes used by APIs for quota/billing.
The server understood the request but refuses to authorize it.
The requested resource could not be found.
The request method is not supported for the resource.
The resource cannot produce content matching the Accept headers.
The server timed out waiting for the request.
The request conflicts with the current state of the server.
The resource is no longer available and will not be available again.
The request is larger than the server is willing to process.
The request entity has a media type the server does not support.
The server refuses to brew coffee because it is, permanently, a teapot.
The request was well-formed but had semantic errors.
The user has sent too many requests in a given amount of time (rate limiting).
Header fields are too large for the server to process.
The resource is unavailable due to legal demands.
A generic error message for an unexpected server condition.
The server does not recognize the request method.
The server, acting as a gateway, received an invalid response upstream.
The server is not ready to handle the request (overloaded or down).
The gateway did not receive a timely response from the upstream server.
The server does not support the HTTP protocol version used.
The client needs to authenticate to gain network access.