The Hyper Text Coffee Pot Control Protocol (HTCPCP) is a facetious communication protocol for controlling, monitoring, and diagnosing coffee pots. It is specified in RFC 2324, published on 1 April 1998 as an April Fools' Day RFC,[2] as part of an April Fools prank.[3] An extension, HTCPCP-TEA, was published as RFC 7168 on 1 April 2014[4] to support brewing teas, which is also an April Fools' Day RFC.
RFC 2324 was written by Larry Masinter, who describes it as a satire, saying "This has a serious purpose – it identifies many of the ways in which HTTP has been extended inappropriately."[5] The wording of the protocol made it clear that it was not entirely serious; for example, it notes that "there is a strong, dark, rich requirement for a protocol designed espressoly [sic] for the brewing of coffee".
Despite the joking nature of its origins, or perhaps because of it, the protocol has remained as a minor presence online. The editor Emacs includes a fully functional client side implementation of it,[6] and a number of bug reports exist complaining about Mozilla's lack of support for the protocol.[7] Ten years after the publication of HTCPCP, the Web-Controlled Coffee Consortium (WC3) published a first draft of "HTCPCP Vocabulary in RDF"[8] in parody of the World Wide Web Consortium's (W3C) "HTTP Vocabulary in RDF".[9]
On April 1, 2014, RFC 7168 extended HTCPCP to fully handle teapots.[4]
Commands and replies
HTCPCP is an extension of HTTP. HTCPCP requests are identified with the Uniform Resource Identifier (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. Using POST for this purpose is deprecated. A new HTTP request header field "Accept-Additions" is proposed, supporting optional additions including Cream, Whole-milk, Vanilla, Raspberry, Whisky, Aquavit, etc.
The HTCPCP server is unable to provide the requested addition for some reason; the response should indicate a list of available additions. The RFC observes that "In practice, most automated coffee pots cannot currently provide additions."
418 I'm a teapot
The HTCPCP server is a teapot; the resulting entity body "may be short and stout" (a reference to the song "I'm a Little Teapot"). Demonstrations of this behaviour exist.[1][10]
Save 418 movement
On 5 August 2017, Mark Nottingham, chairman of the IETFHTTPBIS Working Group, called for the removal of status code 418 "I'm a teapot" from the Node.js platform, a code implemented in reference to the original 418 "I'm a teapot" established in Hyper Text Coffee Pot Control Protocol.[11] On 6 August 2017, Nottingham requested that references to 418 "I'm a teapot" be removed from the programming language Go[12] and subsequently from Python's Requests[13] and ASP.NET's HttpAbstractions library[14] as well.
In response, 15-year-old developer Shane Brunswick created a website, save418.com,[15] and established the "Save 418 Movement", asserting that references to 418 "I'm a teapot" in different projects serve as "a reminder that the underlying processes of computers are still made by humans". Brunswick's site went viral in the hours following its publishing, garnering thousands of upvotes on the social platform Reddit,[16] and causing the mass adoption of the "#save418" Twitter hashtag he introduced on his site. Heeding the public outcry, Node.js, Go, Python's Requests, and ASP.NET's HttpAbstractions library decided against removing 418 "I'm a teapot" from their respective projects. The unanimous support from the aforementioned projects and the general public prompted Nottingham to begin the process of having 418 marked as a reserved HTTP status code,[17] ensuring that 418 will not be replaced by an official status code for the foreseeable future.
On 5 October 2020, Python 3.9 released with an updated http library including 418 IM_A_TEAPOT status code.[18] In the corresponding pull request, the Save 418 movement was directly cited in support of adoption.[19]
Usage
The status code 418 is sometimes returned by servers when blocking a request, instead of the more appropriate 403 Forbidden.[20] Around the time of the 2021–2022 Russo-Ukrainian crisis, the Russian military website mil.ru returned the HTTP 418 status code when accessed from outside of Russia as a DDoS attack protection measure.[21][22] The change was first noticed in December of 2021.[23]
^ abReddington, Joseph, , archived from the original on 2015-09-06, retrieved 2014-10-18
^"Request for Comments 2324", Network Working Group, IETF, from the original on 2012-04-04, retrieved 2012-03-20
^DeNardis, Laura (30 September 2009). Protocol Politics: The Globalization of Internet Governance. MIT Press. pp. 27ff. ISBN978-0-262-04257-4. Retrieved 8 May 2012.
^ abNazar, Imran (April 2014), "Request for Comments 7168", The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA), IETF, from the original on 2014-05-29, retrieved 2014-04-22
^"Emacs extension: coffee.el", Emarsden, Chez, from the original on 2009-02-01, retrieved 2009-02-10.
^"Bug 46647 – (coffeehandler) HTCPCP not supported (RFC2324)", Bugzilla, Mozilla, from the original on 2011-05-14, retrieved 2005-12-21
^HTCPCP Vocabulary in RDF – WC3 RFC Draft, Chief Arabica (Web-Controlled Coffee Consortium), 1 April 2008, from the original on 15 May 2021, retrieved 27 April 2017 – via github
^Koch, Johannes (ed.), HTTP Vocabulary in RDF, et al, W3, from the original on 15 October 2009, retrieved 17 August 2009
^. Archived from the original on 2014-12-06. Retrieved 2014-07-26.
^Nottingham, Mark. "418 I'm A Teapot #14644". from the original on 2017-08-10. Retrieved 2017-08-12 – via github.
^Nottingham, Mark. "net/http: remove support for status code 418 I'm a Teapot". from the original on 2017-08-10. Retrieved 2017-08-12 – via github.
^Nottingham, Mark. "418 418 I'm a Teapot #4238". from the original on 2021-05-15. Retrieved 2017-08-12 – via github.
^Nottingham, Mark. "418 I'm a Teapot #915". from the original on 2019-05-10. Retrieved 2017-08-12 – via github.
^Brunswick, Shane. "We are the teapots". The Save 418 Movement. from the original on 2021-05-15. Retrieved 2021-05-15.
^"HTTP Error Code 418 I'm a Teapot is about to be removed from Node. We've gotta do something. [x-post /r/webdev]". from the original on 2017-08-11. Retrieved 2017-08-12 – via reddit.
^Nottingham, Mark. "Reserving 418". from the original on 2017-08-13. Retrieved 2017-08-12 – via github.
^"What's New In Python 3.9 — Python 3.9.0 documentation". Python Documentation. 2020-10-05. from the original on 2020-10-07. Retrieved 2020-10-08.
^"Issue 39507: http library missing HTTP status code 418 "I'm a teapot" – Python tracker". bugs.python.org. from the original on 2020-10-14. Retrieved 2020-10-08.
^"Enable extra web security on a website". DreamHost. Retrieved 2022-12-18.
^"Russia appears to deploy digital defenses after DDoS attacks". The Record by Recorded Future. 2022-02-25. Retrieved 2022-02-26.
^"I Went to a Russian Website and All I Got Was This Lousy Teapot". PCMag. Retrieved 2022-02-28.
^"Russian MoD website blocked for non-Russian IPs | Hacker News".
External links
Google's demo page: Error 418 (I'm a teapot)!?
Package teapot HTCPCP-TEA implementation by David Skinner
hyper, text, coffee, control, protocol, htcpcp, facetious, communication, protocol, controlling, monitoring, diagnosing, coffee, pots, specified, 2324, published, april, 1998, april, fools, part, april, fools, prank, extension, htcpcp, published, 7168, april, . The Hyper Text Coffee Pot Control Protocol HTCPCP is a facetious communication protocol for controlling monitoring and diagnosing coffee pots It is specified in RFC 2324 published on 1 April 1998 as an April Fools Day RFC 2 as part of an April Fools prank 3 An extension HTCPCP TEA was published as RFC 7168 on 1 April 2014 4 to support brewing teas which is also an April Fools Day RFC Hyper Text Coffee Pot Control ProtocolBack end infrastructure of error418 net which implements HTCPCPInternational standardInternet Engineering Task ForceDeveloped byLarry MasinterIntroducedApril 1 1998 1998 04 01 Websiterfc2324Working teapot implementing HTCPCP TEA 1 Contents 1 Protocol 2 Commands and replies 3 Save 418 movement 4 Usage 5 See also 6 References 7 External linksProtocol EditRFC 2324 was written by Larry Masinter who describes it as a satire saying This has a serious purpose it identifies many of the ways in which HTTP has been extended inappropriately 5 The wording of the protocol made it clear that it was not entirely serious for example it notes that there is a strong dark rich requirement for a protocol designed espressoly sic for the brewing of coffee Despite the joking nature of its origins or perhaps because of it the protocol has remained as a minor presence online The editor Emacs includes a fully functional client side implementation of it 6 and a number of bug reports exist complaining about Mozilla s lack of support for the protocol 7 Ten years after the publication of HTCPCP the Web Controlled Coffee Consortium WC3 published a first draft of HTCPCP Vocabulary in RDF 8 in parody of the World Wide Web Consortium s W3C HTTP Vocabulary in RDF 9 On April 1 2014 RFC 7168 extended HTCPCP to fully handle teapots 4 Commands and replies EditHTCPCP is an extension of HTTP HTCPCP requests are identified with the Uniform Resource Identifier 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 Using POST for this purpose is deprecated A new HTTP request header field Accept Additions is proposed supporting optional additions including Cream Whole milk Vanilla Raspberry Whisky Aquavit etc GET Retrieves coffee from the HTCPCP server PROPFIND Returns 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 provide the requested addition for some reason the response should indicate a list of available additions The RFC observes that In practice most automated coffee pots cannot currently provide additions 418 I m a teapot The HTCPCP server is a teapot the resulting entity body may be short and stout a reference to the song I m a Little Teapot Demonstrations of this behaviour exist 1 10 Save 418 movement EditOn 5 August 2017 Mark Nottingham chairman of the IETF HTTPBIS Working Group called for the removal of status code 418 I m a teapot from the Node js platform a code implemented in reference to the original 418 I m a teapot established in Hyper Text Coffee Pot Control Protocol 11 On 6 August 2017 Nottingham requested that references to 418 I m a teapot be removed from the programming language Go 12 and subsequently from Python s Requests 13 and ASP NET s HttpAbstractions library 14 as well In response 15 year old developer Shane Brunswick created a website save418 com 15 and established the Save 418 Movement asserting that references to 418 I m a teapot in different projects serve as a reminder that the underlying processes of computers are still made by humans Brunswick s site went viral in the hours following its publishing garnering thousands of upvotes on the social platform Reddit 16 and causing the mass adoption of the save418 Twitter hashtag he introduced on his site Heeding the public outcry Node js Go Python s Requests and ASP NET s HttpAbstractions library decided against removing 418 I m a teapot from their respective projects The unanimous support from the aforementioned projects and the general public prompted Nottingham to begin the process of having 418 marked as a reserved HTTP status code 17 ensuring that 418 will not be replaced by an official status code for the foreseeable future On 5 October 2020 Python 3 9 released with an updated http library including 418 IM A TEAPOT status code 18 In the corresponding pull request the Save 418 movement was directly cited in support of adoption 19 Usage EditThe status code 418 is sometimes returned by servers when blocking a request instead of the more appropriate 403 Forbidden 20 Around the time of the 2021 2022 Russo Ukrainian crisis the Russian military website mil ru returned the HTTP 418 status code when accessed from outside of Russia as a DDoS attack protection measure 21 22 The change was first noticed in December of 2021 23 See also EditTrojan Room coffee pot Internet of things List of HTTP status codes 4xx client errorsReferences Edit a b Reddington Joseph Illustrated implementation of Error 418 archived from the original on 2015 09 06 retrieved 2014 10 18 Request for Comments 2324 Network Working Group IETF archived from the original on 2012 04 04 retrieved 2012 03 20 DeNardis Laura 30 September 2009 Protocol Politics The Globalization of Internet Governance MIT Press pp 27ff ISBN 978 0 262 04257 4 Retrieved 8 May 2012 a b Nazar Imran April 2014 Request for Comments 7168 The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances HTCPCP TEA IETF archived from the original on 2014 05 29 retrieved 2014 04 22 Masinter Larry IETF RFCs Archived from the original on 2013 03 27 Emacs extension coffee el Emarsden Chez archived from the original on 2009 02 01 retrieved 2009 02 10 Bug 46647 coffeehandler HTCPCP not supported RFC2324 Bugzilla Mozilla archived from the original on 2011 05 14 retrieved 2005 12 21 HTCPCP Vocabulary in RDF WC3 RFC Draft Chief Arabica Web Controlled Coffee Consortium 1 April 2008 archived from the original on 15 May 2021 retrieved 27 April 2017 via github Koch Johannes ed HTTP Vocabulary in RDF et al W3 archived from the original on 15 October 2009 retrieved 17 August 2009 A Goblin Teasmade teamaker with an implementation of Error 418 Archived from the original on 2014 12 06 Retrieved 2014 07 26 Nottingham Mark 418 I m A Teapot 14644 Archived from the original on 2017 08 10 Retrieved 2017 08 12 via github Nottingham Mark net http remove support for status code 418 I m a Teapot Archived from the original on 2017 08 10 Retrieved 2017 08 12 via github Nottingham Mark 418 418 I m a Teapot 4238 Archived from the original on 2021 05 15 Retrieved 2017 08 12 via github Nottingham Mark 418 I m a Teapot 915 Archived from the original on 2019 05 10 Retrieved 2017 08 12 via github Brunswick Shane We are the teapots The Save 418 Movement Archived from the original on 2021 05 15 Retrieved 2021 05 15 HTTP Error Code 418 I m a Teapot is about to be removed from Node We ve gotta do something x post r webdev Archived from the original on 2017 08 11 Retrieved 2017 08 12 via reddit Nottingham Mark Reserving 418 Archived from the original on 2017 08 13 Retrieved 2017 08 12 via github What s New In Python 3 9 Python 3 9 0 documentation Python Documentation 2020 10 05 Archived from the original on 2020 10 07 Retrieved 2020 10 08 Issue 39507 http library missing HTTP status code 418 I m a teapot Python tracker bugs python org Archived from the original on 2020 10 14 Retrieved 2020 10 08 Enable extra web security on a website DreamHost Retrieved 2022 12 18 Russia appears to deploy digital defenses after DDoS attacks The Record by Recorded Future 2022 02 25 Retrieved 2022 02 26 I Went to a Russian Website and All I Got Was This Lousy Teapot PCMag Retrieved 2022 02 28 Russian MoD website blocked for non Russian IPs Hacker News External links EditGoogle s demo page Error 418 I m a teapot Package teapot HTCPCP TEA implementation by David Skinner save418 com error418 net Archived 2021 01 07 at the Wayback Machine Retrieved from https en wikipedia org w index php title Hyper Text Coffee Pot Control Protocol amp oldid 1133249586, wikipedia, wiki, book, books, library,
