The Response Codes are mostly three-digit codes, which are issued by the server in order to respond to the browser-side request from the client’s side. These status codes run to work as a mean of quicker and more concise communication on how well the server has worked and the current response to the client’s chosen request.
These codes are noted to include some other codes within the list and those are IETF Request for Comments, some specifications, added codes as used in common HTTP applications, and more.
It is the task of the Internet Assigned Numbers Authority to maintain the HTTP status codes’ official registry. Among the 3 digits code, the first digit will talk about the category of status code. Then you have the last two digits, assigned toward a specified response within a given category.
Overall, there are 5 different categories, which can be placed under the response code. These categories are mostly classified depending on the response type of the server, such as communicating with the client.
Updated on: 16.12.2022
Name: Response Code
Referred to as: HTTP Response Code, Successful responses, Redirection messages, Client error responses, Server error responses
Correct Use: n/a
Also known as the web server response code, the HTTP Response codes indicate if the specified HTTP request has been completed in a successful manner. The responses are mostly grouped under five different classes for better understanding.
- 100 Continue: This response mostly indicates that the client should continue with the request or ignore it if the request is finished already.
- 101 Switching protocols: This code is sent to upgrade the request header from the client and indicates the protocol that the server is moving towards.
- 102 Processing: It indicates that the server has received and processed the request, but not requested is yet made available.
- 103 Early hints: It is worked out to be used with the Link header and letting the user agent start preloading the resources.
- 200 Ok: This request has been succeeded. It means that the “success” of it solely depends on the HTTP method of GET, HEAD, PUT or POST, and TRACE.
- 201 Created: In this request succeeded, a new resource will be created as a result. It is mostly the response sent once the post requests or some put requests.
- 202 Accepted: Such requests have been received but not worked upon yet. It is mainly noncommittal as there is no way in HTTP to send an asynchronous response later to indicate the outcome of the request.
- Some of the other versions available under this sector are 203 Non-authoritative Information, 204 No Content, 205 reset content, 206 partial content, and more.
3XX – Redirection code:
This category mainly talks about the fact that the client might take up some added action for completing the request in question. Most of the time, the added action is to redirect the user to another chosen URL. Most of the status codes within the such category are used in URL redirection.
4XX – Client error code:
This category talks about the request that cannot be fulfilled because of an error from the client’s side. The request might have a bad syntax or even authorization lacking from it. The server must have an entity with an explanation of the error situation and if it is a permanent or a temporary condition.
5XX – Server error code:
It ensures that the server has actually encountered an error or is not capable of performing the valid request. The server must have an entity with an explanation of the chosen error situation. It should indicate if it is a permanent or a temporary condition.
The HTTP response codes or the status codes are sent by the web servers in order to respond to the HTTP requests. These status codes signal that the webpage you are working with is OK or might present you with a red flag. It is a vital part of the SEO section. A search engine must be able to crawl, parse, index, and serve the specified URL properly with the content.
- Always understand the purpose before you aim to work on the response code.
- Always check out the code before proceeding further
- Always get to mention the minor things
- Do not review the code without any context as that tends to result in low-level and minor comments
- Make sure to never review the code while it is in the browser
- Never leave minor issues unattended for a long time
Always remember that the success response to an HTTP response code should be 200 or OK in case the response consists of an entity describing the status. It will be 202 or Accepted in case the action has been not worked on yet and 204 or No Content if the action has been worked on but the response fails to add an entity.
What Google Says:
What experts say: