Where To Find A Complete Guide Of HTTP Status Codes?

HTTP status codes are important for both web developers and site users. They provide insight into whether a request was successful, and if not, why not. However, there are so many different codes that it can be difficult to keep track of them all. Luckily, we have compiled a complete guide of HTTP status codes for you. In this guide, we will cover everything from the most common codes to the more obscure ones. We will also provide explanations for what each code means and when you might see it. After reading this guide, you will be an expert on status codes!

List of HTTP status codes


The following is a list of status codes:


100 – Continue

101 – Switching Protocols

102 – Processing (WebDAV)

200 – OK

201 – Created

202 – Accepted

203 – Non-Authoritative Information

204 – No Content

205 – Reset Content

206 – Partial Content

207 – Multi-Status (WebDAV)

208 – Already Reported (WebDAV) 2009]

226 – IM Used


1xx Informational


The 1xx Informational class of status code indicates that the client's request was received, and the server is continuing to process the request.


This class of status code is intended for situations in which the client may want to know about the progress of its request. For example, a client might make a POST request to upload a large file, and receive a 100 Continue response to indicate that the initial part of the request was received successfully.



If the client receives a 100 Continue response, it should continue sending the request body until it receives a final response from the server.


2xx Success


HTTP status codes in the 2xx range indicate that the client's request was successfully received, understood, and accepted.


Some of the most common 2xx status codes are:


200 OK: The request was successful and the response contains the desired information.


201 Created: The request has been fulfilled and a new resource has been created.


202 Accepted: The request has been accepted for processing, but the processing has not been completed.


203 Non-Authoritative Information: The server successfully processed the request, but is returning information from another source.


204 No


3xx Redirection


When a client makes an HTTP request, the server may respond with a 3xx status code to indicate that further action needs to be taken by the client in order to complete the request. This category of status codes indicates that the client must take some additional action in order to complete the request. For example, if a client requests a resource that has moved to a different location, the server may respond with a 301 status code and include the new location of the resource in the response headers.


Some common 3xx status codes include:


301 - Moved permanently

302 - Found (Previously "Moved temporarily")

304 - Not modified

307 - Temporary redirect


If you're seeing a 3xx status code in your web browser, it means that your browser is taking some additional action in order to fetch the resources that you've requested. In most cases, this simply means that your browser is following a redirect from one URL to another. However, it's also possible for a 3xx status code to indicate an error condition.


4xx Client Error



The 4xx class of status code is intended for situations in which the client seems to have erred. For example, a status code of 400 indicates a bad request, while a status code of 404 indicates that the requested resource could not be found.


In general, a 4xx status code means that there was a problem with the request that was made. The most common 4xx status codes are:


400 - Bad Request

401 - Unauthorized

402 - Payment Required

403 - Forbidden

404 - Not Found

405 - Method Not Allowed

406 - Not Acceptable

407 - Proxy Authentication Required

408 - Request Timeout

409 - Conflict

410 - Gone


5xx Server Error


If you receive a 5xx Server Error message, it means that the server is currently unavailable. This can be due to a variety of reasons, such as the server being down for maintenance or overloaded with traffic. If you see this error message, please try again later.


Conclusion


If you are looking for a comprehensive guide of HTTP status codes, then look no further. This article has everything you need to know about the various types of status codes and what they mean. Armed with this knowledge, you will be able to troubleshoot any problems you may have with your website or web application. So what are you waiting for? Start reading and learn all about HTTP status codes today!


Comments