HTTP status cats by GirlieMac: classic server error codes, now with cats


24 Responses to “HTTP status cats by GirlieMac: classic server error codes, now with cats”

  1. nixiebunny says:

    Yup, the internet is hereby won. Forbidden, indeed!

  2. SaberUK says:

    Bush eats kittens? I always knew he was pure evil!

  3. 20tauri says:

    Bahaha! Nice one. Thanks, Xeni :)

  4. love66866 says:

    it’s so long…

  5. failquail says:

    Boingboing now MUST have these error codes configured onto the boingboing servers as defaults :)

  6. awillett says:

    What failquail said. Pretty please?

  7. J Schreiber says:

    FTW! I’m going to quickly add these to apache

  8. Ken Snider says:

    These versus the 2007 variant: – FIGHT!

  9. SoItBegins says:

    EEEEEEEE I love them.

    Now, we just have to convince Microsoft to add these to IIS.

  10. Ryan_T_H says:

    The ’406 – Not Acceptable’ one in the Flickr feed is the best of the lot. Go see it then come back here and laugh.

  11. shedside says:

    Marvellous! Couldn’t resist a stab at filling in the blanks.  Here’s my humble contribution to the genre:

  12. TheMudshark says:

    I lol´d.

  13. jeremy slawson says:

    599 Network connect timeout error duly posted on the wall. I work for a communications company…

  14. William B says:

    I submit to you the often forgotten 418 code which actually has been implemented by at least the BBC.

  15. Kitty says:

    Very funny.  No 301s?

  16. OgilvyTheAstronomer says:

    Heh, that’s brilliant. Going to bed a little happier than I woke up.

  17. OMG. I never giggled so much. *wipes tears from eyes*

  18. And I will SO use some of these to make up my own custom error pages, and hope that people get as many errors as possible visiting my site, LOL.

  19. Adrian Land says:

    I just realised how much of a geek I am that I found that funny.

  20. NobleBaker says:

    301, 318, and more are there if you follow the link to the flickr stream…

Leave a Reply