HTTP is the protocol which serves as the foundation for the web as we know it. From Facebook, to Google, to the page you are browsing right now, almost every task you perform on the web happens thanks to HTTP. And for every response returned to you from a web server via HTTP, the header contains a short numeric status at the very beginning before any of the content you requested. If you spend much time at all online you are probably familiar with the 404 status code: File Not Found, which is by far the most common one seen by users.
While seeing a 404 error in your browser is typically a frustrating experience when you are looking for something that seems to have mysteriously vanished into thin air, here is a light-hearted take on some of the more common HTTP status codes (both “good” and “bad”) as cats. That’s right, cats. Enjoy!
The requested resource could not be found but may be available again in the future. Subsequent requests by the client are permissible.
A generic error message, given when no more specific message is suitable.
The requested resource is only capable of generating content not acceptable according to the Accept headers sent in the request.
Similar to 403 Forbidden, but specifically for use when authentication is possible but has failed or not yet been provided. The response must include a WWW-Authenticate header field containing a challenge applicable to the requested resource. See Basic access authentication and Digest access authentication.
Standard response for successful HTTP requests. The actual response will depend on the request method used. In a GET request, the response will contain an entity corresponding to the requested resource. In a POST request the response will contain an entity describing or containing the result of the action.
Find these and others at httpstatuscats.com