Info

HTTP Status Codes

The standard HTTP response status codes, grouped by class, with what each one means.

Filter

1xx Informational

Code	Reason phrase	Meaning
100	Continue	The initial part of a request has been received and the client should continue sending the rest.
101	Switching Protocols	The server agrees to switch protocols as requested by the client (e.g. to WebSocket).
102	Processing	The server has accepted the request but processing is not yet complete.
103	Early Hints	Lets the client start preloading resources while the server prepares the final response.

2xx Success

Code	Reason phrase	Meaning
200	OK	The request succeeded.
201	Created	The request succeeded and a new resource was created as a result.
202	Accepted	The request has been accepted for processing, but processing is not finished.
203	Non-Authoritative Information	The response was returned by a proxy and may differ from the origin server’s response.
204	No Content	The request succeeded but there is no content to send in the response body.
205	Reset Content	Tells the client to reset the document that sent the request.
206	Partial Content	Returns only part of a resource, as requested via a Range header.

3xx Redirection

Code	Reason phrase	Meaning
300	Multiple Choices	The request has more than one possible response; the client should pick one.
301	Moved Permanently	The resource has permanently moved to a new URL given in the response.
302	Found	The resource temporarily resides at a different URL.
303	See Other	The response to the request can be found at another URL using a GET request.
304	Not Modified	The cached version of the resource is still valid; no need to retransmit it.
307	Temporary Redirect	Like 302, but guarantees the method and body of the original request are repeated.
308	Permanent Redirect	Like 301, but guarantees the method and body of the original request are repeated.

4xx Client Error

Code	Reason phrase	Meaning
400	Bad Request	The server cannot process the request due to a client-side error (malformed syntax, etc).
401	Unauthorized	Authentication is required and has failed or not yet been provided.
403	Forbidden	The client is authenticated but does not have permission to access the resource.
404	Not Found	The server can’t find the requested resource.
405	Method Not Allowed	The request method is not supported for the requested resource.
406	Not Acceptable	No response matches the list of acceptable formats given by the client.
408	Request Timeout	The server timed out waiting for the request from the client.
409	Conflict	The request conflicts with the current state of the target resource.
410	Gone	The requested resource is permanently gone and no forwarding address is known.
411	Length Required	The server refuses the request because a required Content-Length header is missing.
413	Payload Too Large	The request body is larger than the server is willing or able to process.
414	URI Too Long	The requested URL is longer than the server is willing to interpret.
415	Unsupported Media Type	The request body’s media format isn’t supported by the server.
418	I’m a Teapot	An April Fools’ joke from RFC 2324 — the server refuses to brew coffee because it is a teapot.
422	Unprocessable Content	The request is well-formed but contains semantic errors the server can’t process.
425	Too Early	The server is unwilling to process a request that might be replayed.
429	Too Many Requests	The client has sent too many requests in a given time period (rate limiting).
431	Request Header Fields Too Large	The request’s header fields are too large for the server to process.
451	Unavailable For Legal Reasons	The resource is withheld due to a legal demand, such as government censorship.

5xx Server Error

Code	Reason phrase	Meaning
500	Internal Server Error	The server encountered an unexpected condition and could not complete the request.
501	Not Implemented	The server doesn’t support the functionality required to fulfill the request.
502	Bad Gateway	A server acting as a gateway received an invalid response from an upstream server.
503	Service Unavailable	The server isn’t ready to handle the request, often due to overload or maintenance.
504	Gateway Timeout	A gateway server did not get a response in time from an upstream server.
505	HTTP Version Not Supported	The HTTP version used in the request isn’t supported by the server.
507	Insufficient Storage	The server can’t store the representation needed to complete the request.
508	Loop Detected	The server detected an infinite loop while processing the request.
511	Network Authentication Required	The client needs to authenticate to gain network access (e.g. a captive portal).