How dare you, says the angel, he crashes down from the heights

[venta]

I just tried to sign into twitter. I got the following error message:

403 Forbidden: The server understood the request, but is refusing to fulfill it.

Now, that's an HTTP status code I've seen plenty of times before. I don't think, though, I've ever seen an error that made the server seem quite so petulant.

Coming up soon:

404 Not Found: If you don't know where you put it, the server doesn't see why it should have to tell you.

Comments

[lnr]

:)

[undyingking.livejournal.com]

This is actually Tim B-L et al's original wording for the status code.

[ewx.livejournal.com]

Reminds me of

[beckyl.livejournal.com]

Ah, context - now I remember who you are when you're not on venta's LJ and why I vaguely recognise that entity!

[drdoug.livejournal.com]

301 Moved Permanently: No no no, it's not there, it's over *here*

500 Internal Server Error: Server is sulking.

502 Bad Gateway: No biscuit.

[hjalfi.livejournal.com]

The granddaddy of all web servers, httpd, also contains the snarky:

403: Forbidden - URL containing .. forbidden [don't try to break in]

...the annoyed:

404: Not found - file doesn't exist or is read protected [even tried multi]

...and the overbearing:

403: Forbidden - by rule

And, of course, who can forget that traditional Unix error message:

Printer on fire

[beckyl.livejournal.com]

'Out of paper on Drive C:'

[ulfilias.livejournal.com]

*grin*

I love cute error messages.