
A Quick Guide to HTTP Status Codes with Infographics


HTTP Status Code is returned when an HTTP request is made to the server. The server returns an HTTP Status Code in response to your request.
There are five classes of HTTP Status Code as following.
- Informational โ 1XX
- Success โ 2XX
- Redirection โ 3XX
- Client Error โ 4XX
- Server Error โ 5XX
Letโs take a look at the below diagram, which gives an idea of how a status code is returned from the webserver.
So now, you have an idea of how the status code is generated, and here are some of the popular HTTP status return codes in Infographics.
Success Response
200 โ OK:ย The standard HTTP response for successful HTTP requests. In another way, the webserver will return 200 when the requested content is served successfully.
202 โ Accepted:ย The server has accepted your request and yet to process them.
206 โ Partial Content:ย Only partial content is delivered due to the range header sent by a client like wget.
Redirection Response
301 โ Moved permanently:ย Your requested page has been moved permanently to a new location. This instructs search engine bot to crawl a new location.
302 โ Moved temporarily:ย Your request is served from a different location, but that is a temporary arrangement. This instructs the search engine bot to crawl the original location.
305 โ Use proxy:ย The requested resource is only available through a proxy. That means you must use a relevant proxy to get the requested page successfully.
304 โ Not modified:ย Usually, when the cached page is served when a resource has not been modified.
Client Error
400 โ Bad request:ย The server is confused about what you have requested. Probably bad syntax or trying to include characters in URI, which server doesnโt understand.
401 โ Not authorized:ย The requested page is protected and requires authentication. You must log in in order to get the requested page successfully.
403 โ Forbidden:ย You have to try to access which you donโt have permission. This, not necessary resource is protected by the password; it could also be when files/folder permission doesnโt allow viewing the requested page.
404 โ Not found:ย Probably the most famous one โ your requested page is not found on the server. You are trying to access something, which doesnโt exist.
405 โ Method not allowed:ย You are requesting a page with the wrong method. For example, you are doing GET on POST data. Or you are trying the method, which is disabled, for example โ TRACE, PUT, DELETE.
408 โ Request timeout:ย The server timed out waiting for the request
411 โ Length required:ย Your request doesnโt meet the length of its content, which is required by the requested resource.
Server Error
500 โ Internal server error:ย A very generic error when the server encountered an error due to various reasons. Logs must be examined to see why the server has responded to an internal error.
502 โ Bad gateway:ย The server was acting as a gateway or proxy and received an invalid response from the upstream server like Tomcat, WebSphere.
503 โ Service unavailable:ย The server canโt serve your request. This could be due to either server is too busy in other stuff or almost dead.
I hope now you have an idea about the HTTP status return code if you find this useful, help in sharing with your friends.
More great readings on Sysadmin
-
Looking For Traceroute on RHEL 8? Try TracepathAbhishek Nair on June 14, 2022
-
6 Best Switch Port Monitoring ToolsDurga Prasad Acharya on June 12, 2022
-
Windows 10/11 Random Shutdown: How to Find the CauseHitesh Sant on May 30, 2022
-
7 Best Server Configuration Monitoring and Auditing ToolsTalha Khalid on May 28, 2022
-
8 Best FTP Server Software for Windows for Secure TransferSatish Shethi on May 24, 2022
-
OSI Model Layers: An Introduction GuideAmrita Pathak on May 13, 2022
Join Geekflare Newsletter
Every week we shareย trending articlesย andย toolsย in our newsletter. More than 10,000 people enjoy reading, and you will love it too.