Oh. My. Gods.
When I get my domain and such up and running, I am Sooooo making these the default error scripting. From Wikipedia HTCPCP
HTCPCP is specified in the jocular RFC 2324, published on April 1, 1998. Although the RFC describing the protocol is an April Fools’ Day joke and not to be taken seriously, it specifies the protocol itself accurately enough for it to be a real, non-fictional protocol. The powerful editor Emacs actually includes a fully functional implementation of it, and a number of patches exist to extend Mozilla in this direction.
HTCPCP is an extension of HTTP. HTCPCP requests are identified with the URI scheme
coffee:(or the same word in any other of the 29 listed languages) and contain several additions to the HTTP methods:
POST: Causes the HTCPCP server to brew coffee.
GET: Retrieves coffee from the HTCPCP server.
PROPFIND: Finds out metadata about the coffee.
WHEN: Says “when”, causing the HTCPCP server to stop pouring milk into the coffee (if applicable).
It also defines two error responses:
406 Not Acceptable: The HTCPCP server is unable to brew coffee for some reason. The response should indicate a list of acceptable coffee types.
418 I'm a teapot: The HTCPCP server is a teapot. The responding entity MAY be short and stout.
As Stefan Moebius noted, the HTCPCP does not define the error response for Out of Coffee.
Isn’t that just GREAT!? Oh here’s one more link about it. I am just… wow… Coffee…
More Info on the Coffee Protocol [Excerpt Below]
1. Rationale and Scope
There is coffee all over the world. Increasingly, in a world in which
computing is ubiquitous, the computists want to make coffee. Coffee
brewing is an art, but the distributed intelligence of the web-
connected world transcends art. Thus, there is a strong, dark, rich
requirement for a protocol designed espressoly for the brewing of
coffee. Coffee is brewed using coffee pots. Networked coffee pots
require a control protocol if they are to be controlled.
Increasingly, home and consumer devices are being connected to the
Internet. Early networking experiments demonstrated vending devices
connected to the Internet for status monitoring [COKE]. One of the
first remotely _operated_ machine to be hooked up to the Internet,
the Internet Toaster, (controlled via SNMP) was debuted in 1990
The demand for ubiquitous appliance connectivity that is causing the
consumption of the IPv4 address space. Consumers want remote control
of devices such as coffee pots so that they may wake up to freshly
brewed coffee, or cause coffee to be prepared at a precise time after
the completion of dinner preparations.