What is HTTP Response Codes?

HTTP status codes are standard response codes provided by website servers over the internet. These status codes help to recognize the root of the problem when a resource does not load correctly. Those response codes are sometimes called HTTP error codes or internet error codes.

More Information on HTTP Status Codes

HTTP 502: Bad Getaway. HTTP 404: File Not Found. Do these words sound familiar? These are probably some of the most common HTTP response codes that we encounter maybe on a daily basis. These are not the only HTTP status codes there is. In fact, there is a plethora of them, from 100 to 599, all bearing specific news to whoever needs to hear them: log administrations, website visitors, programmers. These codes are part of specific language that will help those that run the World Wide Web in making it a well-oiled machine that links everyone online.

HTTP Response Codes

But why should you know all about HTTP response code? These HTTP error codes already appear alien to you; for some, a simple HTTP 502 or HTTP 404 error already baffles them. Here at BelugaCDN, we see the value of being tech-savvy, not only at the individual sense but also at the professional sense, especially for potential CDN clients like you and the workforce you wish to support. This kind of knowledge also puts you at an advantage when it comes to using technology side-by-side with business. With the knowledge of HTTP response codes, server logs make better sense to you, and you can avail of more specific technology solutions than specific ones that everyone uses. On that note, let’s start your journey with proficiency in HTTP status code.

List of HTTP Response Status Codes

  • 1xx informational response – Request received and continuing process
  • 2xx successful – Request received, understood and accepted
  • 3xx redirection – Additional action needs to be taken to meet the request
  • 4xx client error – Request holds bad syntax
  • 5xx server error – Server failed to meet a valid request

100 – 199: Informational Codes

HTTP response codes in this family are just for mere information, only to identify that a specific process has been finished or a request has been completed. It is rare that HTTP status codes within this range are used, because most of them specify seemingly mundane processes. Examples of these HTTP status codes include the most basic: 100: Continue, meaning the server is to carry on as usual, and 102: Processing, meaning the request is being handled by either the server or the client (the client is the entity at the receiving end of the request). As you can see, these two informational codes are part of the normal process, by why the need to identify HTTP response code for them? These HTTP codes help on tracking the pathways of data in the entirety of the server’s performance. Without these HTTP status codes, there will be no signposts for specific process, and log viewing turns into a guessing game. HTTP response codes from 100 – 199 have a relevant usage, after all.

200 – 299: Success Codes

HTTP error codes under this family show success in different forms. HTTP response codes 200 – 299 are bearers of good news: the request has been accepted, a new request has been created, or a certain problem was solved. As HTTP status codes in the earlier group act as signposts, HTTP status codes in the 200 group act as go signals for specific actions to continue, because needed requests have been made possible. 202: Accepted means that the client received the request. The HTTP response code 202 does not necessarily mean that the request is made, but what is important is that it is being handled. Part of these HTTP status codes is 206: Partial Content. This means that the request is met partially, but met nonetheless.

300 – 399: Redirection Codes

HTTP status codes 300-399 talk about redirection. These HTTP response codes mean that the request had to be redirected, for various reasons. 300 – 399 HTTP status code may need immediate action, because the redirection could be a pending request, and the web browser is stuck somewhere. 300: Multiple Choices makes it confusing for the web browser to choose where to go, so direct action has to be done. 310: Resource Moved Permanently means that from that point on, the route of the request will change for good.

400 – 499: Client Error Codes

We now go to HTTP error codes that may be alarming to some extent. HTTP response codes in the HTTP error 400s mean that the client is not in capacity to complete a request. The most known among the error 400 family of Hypertext Transfer Protocol (HTTP) Status Code is 404: File Not Found. This simply means that the client being contacted is nowhere to be found, thus the request cannot be completed.

500 – 599: Server Error Codes

And finally, the 500 – 599 HTTP status codes, informs the log of problems with the server. Servers are supposed to coordinate with each other, but these Hypertext Transfer Protocol (HTTP) Response Code mean that there might be a problem in how these servers worked together. 502: Bad Gateway simple means that one server received an invalid response from another server. The gravity of this situation may vary, though. But then again, HTTP response codes in the 500 group may need some attention.

And there you have it! That’s your brief look into what HTTP codes are, and what these groups of HTTP status codes mean. That’s a good first step to understand that server log, and you’re on a good start to be well-informed which of these HTTP response codes needs attention, or not.

Power-up your Content Delivery
30 Day Free Trial Cancel Anytime

Get A Free Trial!

Related Resource