Hyper Text Coffee Pot Control Protocol: Difference between revisions

From Wikipedia, the free encyclopedia
Content deleted Content added
fixed name of error response
m recategorizing per WP:CFD using AWB
Line 17: Line 17:
[[Category:Request for Comments]]
[[Category:Request for Comments]]
[[Category:Internet protocols]]
[[Category:Internet protocols]]
[[category:April Fool's Day]]
[[Category:April Fools' Day]]


[[de:Hyper Text Coffee Pot Control Protocol]]
[[de:Hyper Text Coffee Pot Control Protocol]]

Revision as of 17:13, 12 January 2008

The Hyper Text Coffee Pot Control Protocol (HTCPCP for short) is a protocol for controlling, monitoring, and diagnosing coffee pots.

HTCPCP is specified in the jocular RFC 2324, published on April 1 1998. Although the RFC describing the protocol is an April fools 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:

  • BREW or 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 responsing entity may be short and stout.

For more detailed specifications, see the HTCPCP RFC (RFC 2324).