Hyper Text Coffee Pot Control Protocol: Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
external link to demo of 418 error
Line 20: Line 20:
|width="150px" valign=top|<code>406 Not Acceptable</code>||The HTCPCP server is unable to brew coffee for some reason; the response should indicate a list of acceptable coffee types.
|width="150px" valign=top|<code>406 Not Acceptable</code>||The HTCPCP server is unable to brew coffee for some reason; the response should indicate a list of acceptable coffee types.
|-
|-
|<code>418 I'm a teapot</code>||The HTCPCP server is a [[teapot]]; the resulting entity may be [[I'm a Little Teapot|short and stout]]. Demonstrations of this behaviour exist.<ref name=error418>http://www.cs.rhul.ac.uk/home/joseph/teapot.html</ref>
|<code>418 I'm a teapot</code>||The HTCPCP server is a [[teapot]]; the resulting entity may be [[I'm a Little Teapot|short and stout]]. Demonstrations of this behaviour exist.<ref>[http://www.cs.rhul.ac.uk/home/joseph/teapot.html Implementing Error 418]<br />[http://134.219.188.123/ Error 418 implemented]</ref>
|}
|}


Line 27: Line 27:
*[[April Fools' Day RFC]]
*[[April Fools' Day RFC]]
*[[Trojan Room coffee pot]]
*[[Trojan Room coffee pot]]

==External Links==
*[http://134.219.188.123/ http://134.219.188.123/] Demonstration of error 418<ref name=error418></ref>


==References==
==References==

Revision as of 05:30, 23 November 2011

Diagram of a coffee percolator

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 1 April 1998.[1] Although the RFC describing the protocol is an April Fools' Day joke, it specifies the protocol accurately enough for it to be a real, non-fictional protocol. The editor Emacs actually includes a fully functional implementation of it,[2] and a number of bug reports exist complaining about Mozilla's lack of support for the protocol.[3] Ten years after the publication of HTCPCP, the fictional Web-Controlled Coffee Consortium (WC3) published a first draft of "HTCPCP Vocabulary in RDF"[4] in analogy of the World Wide Web Consortium's (W3C) "HTTP Vocabulary in RDF".[5]

Commands and replies

HTCPCP is an extension of HTTP. HTCPCP requests are identified with the URI scheme coffee: (or the corresponding 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 resulting entity may be short and stout. Demonstrations of this behaviour exist.[6]

See also

Wikimedia Commons has media related to Coffee pots.

References

  1. ^ Network Working Group — Request for Comments: 2324
  2. ^ Emacs extension: coffee.el
  3. ^ Bug 46647 — (coffeehandler) HTCPCP not supported (RFC2324) at bugzilla.mozilla.org
  4. ^ Chief Arabica (Web-Controlled Coffee Consortium): HTCPCP Vocabulary in RDF – WC3 RFC Draft 01 April 2008. Accessed 17 August 2009.
  5. ^ Johannes Koch et al (editors): "HTTP Vocabulary in RDF". Accessed 17 August 2009.
  6. ^ Implementing Error 418
    Error 418 implemented
Retrieved from "https://en.wikipedia.org/w/index.php?title=Hyper_Text_Coffee_Pot_Control_Protocol&oldid=462060428"