Server Responses and How to Make Sure You Can Blame Everyone But Yourself

There’s a whole suite of server errors. Sometimes they tell you when you’ve hit an information dead-end and sometimes they tell you when someone is having a bad day.

Thanks to the very fun and not boring Status Code Registry maintained by the equally jazzy Internet Assigned Numbers Authority, we have a defined list of all 63 official responses and code signifies.

For starters we have the 1xx class:

This class defines information responses. But don’t all responses carry information? Well yes. But the 100 class acts as a way of letting developers know that a request has been received and some other action may or may not be needed. The server may be waiting for more information to be sent about the request, the server might be preparing the request, or the server might want to notify the user is being redirected to a different protocol (for instance, HTTP/1.0). All in all, these requests are most often looked for and seen by devs. A user will not see 1xx class responses.

Next is the 2xx class:

You’re in good company! the 200 class consists of all successful responses, the most generic of which is 200. A 200 response simply states that a request was received and a response given. Everyone’s happy. Depending on how the…