📄 List of HTTP status codes.

This is a list of Hypertext Transfer Protocol ( HTTP ) response status codes.

The first digit of the status code specifies one of five standard classes of responses.

All HTTP response status codes are separated into five classes or categories. The first digit of the status code defines the class of response, while the last two digits do not have any classifying or categorization role. There are five classes defined by the standard:

Status Codes
1XX Informational Response	The request was Received, continuing process.
2XX Successful	The request was successfully Received, Understood, and Accepted.
3XX Redirection	Further action needs to be taken in order to complete the request.
4XX Client Error	The request Contains Bad Syntax or Cannot Be Fulfilled.
5XX Server Error	The server Failed to fulfil an apparently Valid Request.

1XX Informational Response:

An informational response indicates that the request was Received and Understood. It alerts the client to wait for a Final Response.

100 Continue	The server has Received the Request Headers and the Client should Proceed to send the request body ( POST Request for example ).
101 Switching Protocols	The requester has asked the server to Switch Protocols and the Server has Agreed to do so.
102 Processing	This code indicates that the Server has Received and is Processing the Request, but No Response is available yet.
103 Early Hints	Used to Return some Response Headers before final HTTP message.

2XX Success:

This class of status codes Indicates the Cction Requested by the Client was Received, Understood, and Cccepted.

200 OK	Standard response for Successful HTTP Requests. In a GET Request, the response will Contain an entity Corresponding to the Requested Resource. In a POST Request, the response will Contain an entity Describing or Containing the result of the Action.
201 Created	The request has been Fulfilled, Resulting in the creation of a New Resource.
202 Accepted	The request has been Accepted for Processing, but the Processing has Not Been Completed. The request Might or Might not be Eventually Acted Upon, and may be Disallowed when Processing Occurs.
203 Non-Authoritative Information	The Server is a Transforming Proxy that Received a 200 from its Origin, but is Returning a Modified Version of the origin's response.
204 No Content	The Server Successfully Processed the Request, and is Not Returning any Content.
205 Reset Content	The Server Successfully Processed the Request, asks that the Requester Reset its Document View, and is Not Returning any Content.
206 Partial Content	The Server is Delivering Only part of The Resource Due to a Range Header Sent by the Client. The Range Header is Used by HTTP Clients to Enable Resuming of Interrupted Downloads, or Split a Download into multiple simultaneous streams.
207 Multi-Status	The Messagee body that Follows is by Default an XML Message and can Contain a Number of Separate Response Codes, Depending on How Many Sub-Requests were Made.
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.

3XX Redirection:

This class of status code Indicates the client Must take Additional Action to complete the Request. Many of these status codes are Used in URL Redirection.

A user agent may carry out the Additional Action with no user interaction only if the method Used in the Second Request is GET or HEAD.

300 Multiple Choices	Indicates Multiple Options for the Resource from which the client may Choose.
301 Moved Permanently	This and all future requests should be Directed to the Given a Uniform Resource Identifier.
302 Found	Tells the Client to Look at Another URL.
303 See Other	The response to the request can be Found under Another Uniform Resource Identifier using the GET Method. When Received in response to a POST or PUT, the client should Presume that the Server has Received the Data and should issue a new GET Request to the Given a Uniform Resource Identifier.
304 Not Modified	Indicates that the Resource has Not Been Modified since the Version Specified by the Request Headers.
305 Use Proxy	The requested Resource is Available Only through a Proxy, the Address for which is Provided in the Response.
306 Switch Proxy	No longer Used.
307 Temporary Redirect	In this case, the Request should be Repeated with Another Uniform Resource Identifier; however, Future Requests should still Use the Original Uniform Resource Identifier.
308 Permanent Redirect	This and All future Requests should be dIrected to the given a Another Uniform Resource Identifier.

4XX Client Error:

This class of Status Code is intended for Situations in which the Error seems to have been Caused By The Client. These Status Codes are applicable to any Request Method.

400 Bad Request	The Server Cannot or will not Process the Request due to an apparent Client Error.
401 Unauthorized	Similar to 403 Error, but specifically for use when Authentication is Required and has Failed or has Not yet been Provided. User does Not Have Valid Authentication Credentials for the Target Resource.
402 Payment Required	The original intention was that this code might be used as part of some form of digital cash or micropayment scheme.
403 Forbidden	The Request contained Valid Data and was Understood by the Server, but the Server is Refusing Action. This code is also typically Used if the Request Provided Authentication by answering the WWW-Authenticate Header field challenge.
404 Not Found	The Requested Resource could Not Be Found but may be Available in the Future.
405 Method Not Allowed	A Request method is Not Supported for the Requested Resource.
406 Not Acceptable	The Requested resource is capable of Generating Only Content Not Acceptable According to the Accept Headers sent in the Request.
407 Proxy Authentication Required	The Client must First Authenticate itself with the Proxy.
408 Request Timeout	The Server timed out Waiting for the Request.
409 Conflict	Indicates that the Request could Not Be Processed because of Conflict in the current State of the Resource.
410 Gone	Indicates that the Resource Requested is No Longer Available and will Not Be Available Again. This should be Used when a Resource Has Been Intentionally Removed and the Resource should be Purged.
411 Length Required	The Request Did Not specify the Length of its Content, which is Required by the Requested Resource.
412 Precondition Failed	The Server Does Not meet one of the Preconditions that the Requester put on the Request Header Fields.
413 Payload Too Large	The Request is Larger than the Server is Willing or Able to Process.
414 URI Too Long	The URI Provided was Too Long for the Server To Process. Often the Result of Too Much Data being encoded as a Query-String of a GET Request, in which case it should be Converted to a POST Request.
415 Unsupported Media Type	The Request entity Has A Media Type which the Server or Resource does Not Support.
416 Range Not Satisfiable	The client has Asked for a Portion of the File, but the Server Cannot Supply that Portion.
417 Expectation Failed	The Server Cannot Meet the Requirements of the Expect Request-Header field.
421	The Request was Directed at a Server that is Not Able to Produce a Response.
422 Unprocessable Entity	The Request was Well-Formed but was unable to be Followed Due to Semantic Errors.
423 Locked	The Resource that is being Accessed is Locked.
424 Failed Dependency	The Request Failed because it Depended on Another Request and that Request Failed.
425 Too Early	Indicates that the Server is Unwilling to Risk Processing a Request that might be Replayed.
426 Upgrade Required	The Client should Switch to a Different Protocol.
428 Precondition Required	The origin Server Requires the Request to be Conditional.
429 Too Many Requests	The User has Sent too Many Requests in a Given Amount of time.
431 Request Header Fields Too Large	The Server is Unwilling to Process the Request because either an Individual Header Field, or All the Header Fields Collectively, are too Large.
451 Unavailable For Legal Reasons	A Server Operator has Received a legal Demand to Deny Access to a Resource or to a set of Resources that includes the Requested Resource.

5XX Server Error:

The Stats Code indicate cases in which the Server is aware that it has Encountered an Error or is otherwise Incapable Of Performing the Request. These response codes are Applicable to Any Request Method.

500 Internal Server Error	A Generic Error Message, given when an Unexpected Condition was Encountered and no more Specific Message is Suitable.
501 Not Implemented	The Server either does Not Recognize the Request Method, or it lacks the ability to Fulfil the Request.
502 Bad Gateway	The Server was acting as a Gateway or Proxy and Received an Invalid Response from the Upstream Server.
503 Service Unavailable	The Server Cannot Handle the Request.
504 Gateway Timeout	The Server was acting as a Gateway or Proxy and Did Not Receive a timely Response from the Upstream Server.
505 HTTP Version Not Supported	The Server does Not Support the HTTP Protocol Version used in the Request.
506 Variant Also Negotiates	Transparent content Negotiation for the Request Results in a Circular Reference.
507 Insufficient Storage	The Server is unable to Store the Representation needed to Complete the Request.
508 Loop Detected	The Server detected an Infinite Loop while Processing the Request.
510 Not Extended	Further Extensions to the Request are Required for the Server to Fulfil it.
511 Network Authentication Required	The Client needs to Authenticate to gain Network Access. Intended for use by Intercepting Proxies used to Control Access to the Network.