Before you go into reading this, checkout the first blog on HTTP Status Codes for maximum comprehension. Done with that? Let’s set the balling rolling for today’s post.
There are a lot of different HTTP status codes and that’s not including the fact that applications can even define their own status codes. Let’s dive into the top 11 most common HTTP responses you are likely to come across as you browse the web and their implications.
Code | Status Response Code Name | Meaning
200 — OK → The request was completed successfully.
201 — Created → A resource has been created (for example a new user or new blog post).
301 — Permanent Redirect →This redirects the client’s browser to a new webpage or tells search engines that the page has been moved somewhere else and you’ve got to look there instead.
302 — Temporary Redirect → Similar to the above permanent redirect, but as the name suggests, this is only a temporary change and it may change again in the near future.
400 — Bad Request → This tells the browser that something was either wrong or missing in their request. This could sometimes be used if the web server’s resource that is being requested expected a certain parameter that the client didn’t attach to their request.
401 — Not Authorized → You are not currently allowed to view this resource until you have authorised with the web application, most commonly with a username and password.
403 — Forbidden →You do not have permission to view this resource whether you are logged in or not.
405 — Method Not Allowed →The resource does not allow this method request, for example, you send a GET request to the resource /create-account when it was expecting a POST request instead.
404 — Page Not Found →The page/resource you requested does not exist.
500 — Internal Service Error →The server has encountered some kind of error with your request that it doesn’t know how to handle properly.
503 — Service Unavailable →This server cannot handle your request as it’s either overloaded or down for maintenance.