Quick reference guide for all HTTP status codes with detailed descriptions
100The server has received the request headers, and the client should proceed to send the request body.
101The requester has asked the server to switch protocols and the server has agreed to do so.
102The server has received and is processing the request, but no response is available yet.
103Used to return some response headers before final HTTP message.
200The request has succeeded. The meaning of success depends on the HTTP method used.
201The request has been fulfilled and resulted in a new resource being created.
202The request has been accepted for processing, but the processing has not been completed.
203The server successfully processed the request but is returning information that may be from another source.
204The server successfully processed the request and is not returning any content.
205The server successfully processed the request, but is not returning any content. Requires requester to reset the document view.
206The server is delivering only part of the resource due to a range header sent by the client.
300Indicates multiple options for the resource that the client may follow.
301This and all future requests should be directed to the given URI.
302The resource was found but at a different URI. The client should continue to use the original URI.
303The response to the request can be found under another URI using a GET method.
304Indicates that the resource has not been modified since the version specified by the request headers.
307The request should be repeated with another URI, but future requests should still use the original URI.
308The request and all future requests should be repeated using another URI.
400The server cannot or will not process the request due to client error (e.g., malformed request syntax).
401Authentication is required and has failed or has not yet been provided.
402Reserved for future use. Originally intended for digital payment systems.
403The request was valid, but the server is refusing to respond to it. Unlike 401, authentication will not help.
404The requested resource could not be found but may be available in the future.
405A request method is not supported for the requested resource.
406The requested resource is capable of generating only content not acceptable according to the Accept headers.
407The client must first authenticate itself with the proxy.
408The server timed out waiting for the request.
409Indicates that the request could not be processed because of conflict in the request.
410Indicates that the resource requested is no longer available and will not be available again.
411The request did not specify the length of its content, which is required by the requested resource.
412The server does not meet one of the preconditions that the requester put on the request.
413The request is larger than the server is willing or able to process.
414The URI provided was too long for the server to process.
415The request entity has a media type which the server or resource does not support.
416The client has asked for a portion of the file, but the server cannot supply that portion.
417The server cannot meet the requirements of the Expect request-header field.
418Any attempt to brew coffee with a teapot should result in the error code "418 I'm a teapot". (April Fools' joke)
421The request was directed at a server that is not able to produce a response.
422The request was well-formed but was unable to be followed due to semantic errors.
423The resource that is being accessed is locked.
424The request failed due to failure of a previous request.
425Indicates that the server is unwilling to risk processing a request that might be replayed.
426The client should switch to a different protocol.
428The origin server requires the request to be conditional.
429The user has sent too many requests in a given amount of time ("rate limiting").
431The server is unwilling to process the request because either an individual header field or all the header fields collectively are too large.
451A server operator has received a legal demand to deny access to a resource or to a set of resources.
500A generic error message when the server encounters an unexpected condition.
501The server either does not recognize the request method, or it lacks the ability to fulfill the request.
502The server was acting as a gateway or proxy and received an invalid response from the upstream server.
503The server is currently unavailable (overloaded or down for maintenance).
504The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.
505The server does not support the HTTP protocol version used in the request.
506Transparent content negotiation for the request results in a circular reference.
507The server is unable to store the representation needed to complete the request.
508The server detected an infinite loop while processing the request.
510Further extensions to the request are required for the server to fulfill it.
511The client needs to authenticate to gain network access.
1xx Informational: Request received, continuing process
2xx Success: The action was successfully received, understood, and accepted
3xx Redirection: Further action must be taken to complete the request
4xx Client Error: The request contains bad syntax or cannot be fulfilled
5xx Server Error: The server failed to fulfill an apparently valid request
Help others discover this tool!
