What are status codes?

This is a listing of Hypertext Transfer Protocol (HTTP) reaction status codes. Status codes are issued with the aid of using a server in reaction to a client's request made to the server.

It consists of codes from IETF Request for Comments (RFCs), different specifications, and a few extra codes utilized in a few common programs of the HTTP. 

The first digit of the reputation code specifies one in every of 5 well-known training responses. The message terms proven are typical, however, any human-readable opportunity can be provided. 

Unless in any other case stated, the reputation code is a part of the HTTP/1.1 well-known (RFC 7231).[1] The Internet Assigned Numbers Authority (IANA) continues the reputable registry of HTTP reputation codes.[2] All HTTP reaction reputation codes are separated into 5 training or categories. The first digit of the reputation code defines the elegance of reaction, at the same time as the closing digits do now no longer have any classifying or categorization role. 

There are 5 training described with the aid of using the standard:

• 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 fulfill an apparently valid request

If you want to learn more information about these five classes. Please visit.

List of HTTP status codes - Wikipedia

Response codes of the Hypertext Transfer Protocol This is a list of Hypertext Transfer Protocol (HTTP) response status codes. Status codes are issued by a server in response to a client's request made to the server. It includes codes from IETF Request for Comments (RFCs), other specifications, and some additional codes used in some common applications of the HTTP. The first digit of the status code specifies one of five standard classes of responses. The message phrases shown are typical, but any human-readable alternative may be provided. Unless otherwise stated, the status code is part of the HTTP/1.1 standard (RFC 7231). [1] The Internet Assigned Numbers Authority (IANA) maintains the official registry of HTTP status codes. [2] 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: 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 is issued on a provisional basis while request processing continues. It alerts the client to wait for a final response. The message consists only of the status line and optional header fields, and is terminated by an empty line. As the HTTP/1.0 standard did not define any 1xx status codes, servers must not [note 1] send a 1xx response to an HTTP/1.0 compliant client except under experimental conditions. [3] 100 Continue The server has received the request headers and the client should proceed to send the request body (in the case of a request for which a body needs to be sent; for example, a POST request). Sending a large request body to a server after a request has been rejected for inappropriate headers would be inefficient. To have a server check the request's headers, a client must send Expect: 100-continue as a header in its initial request and receive a 100 Continue status code in response before sending the body. If the client receives an error code such as 403 (Forbidden) or 405 (Method Not Allowed) then it should not send the request's body. The response 417 Expectation Failed indicates that the request should be repeated without the Expect header as it indicates that the server does not support expectations (this is the case, for example, of HTTP/1.0 servers). [4] 101 Switching Protocols The requester has asked the server to switch protocols and the server has agreed to do so. [5] 102 Processing ( WebDAV ; RFC 2518) A WebDAV request may contain many sub-r

https://en.wikipedia.org/wiki/List_of_HTTP_status_codes#:~:text=Status%20codes%20are%20issued%20by,request%20made%20to%20the%20server.&text=The%20first%20digit%20of%20the%20status%20code%20defines%20the%20class,any%20classifying%20or%20categorization%20role.