Hyper Text Coffee Pot Control Protocol: Difference between revisions

Content deleted Content added

Inline

Revision as of 04:19, 15 May 2021

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.

Protocol

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.
`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

On 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]

References

^ ^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 "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.

External links

Google's demo page: Error 418 (I'm a teapot)!?
Package teapot HTCPCP-TEA implementation by David Skinner
error418.net

[JR-1] Reddington, Joseph, Illustrated implementation of Error 418, archived from the original on 2015-09-06, retrieved 2014-10-18

[2] "Request for Comments 2324", Network Working Group, IETF, archived from the original on 2012-04-04, retrieved 2012-03-20

[3] 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.

[rfc7168-4] "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

[5] Masinter, Larry. "IETF RFCs". Archived from the original on 2013-03-27.

[6] "Emacs extension: coffee.el", Emarsden, Chez, archived from the original on 2009-02-01, retrieved 2009-02-10.

[7] "Bug 46647 – (coffeehandler) HTCPCP not supported (RFC2324)", Bugzilla, Mozilla, archived from the original on 2011-05-14, retrieved 2005-12-21

[8] 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

[9] Koch, Johannes (ed.), HTTP Vocabulary in RDF, et al, W3, archived from the original on 15 October 2009, retrieved 17 August 2009

[10] "A Goblin Teasmade teamaker with an implementation of Error 418". Archived from the original on 2014-12-06. Retrieved 2014-07-26.

[11] Nottingham, Mark. "418 I'm A Teapot #14644". Archived from the original on 2017-08-10. Retrieved 2017-08-12 – via github.

[12] 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.

[13] Nottingham, Mark. "418 418 I'm a Teapot #4238". Archived from the original on 2021-05-15. Retrieved 2017-08-12 – via github.

[14] Nottingham, Mark. "418 I'm a Teapot #915". Archived from the original on 2019-05-10. Retrieved 2017-08-12 – via github.

[15] Brunswick, Shane. "We are the teapots". The Save 418 Movement. Archived from the original on 2021-05-15. Retrieved 2021-05-15.

[16] "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.

[17] Nottingham, Mark. "Reserving 418". Archived from the original on 2017-08-13. Retrieved 2017-08-12 – via github.

[18] "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.

[19] "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.

[1]

[2]

[3]

[4]

[5]

[6]

[7]

[8]

[9]

[10]

[11]

[12]

[13]

[14]

[15]

[16]

[17]

[18]

[19]

@@ Line 2: / Line 2: @@
 [[File:Htcpcp teapot.jpg|thumb|Implementation of HTCPCP at error418.net |alt=]]
 [[File:HTCPCP Pot.jpg|thumb|Working teapot implementing HTCPCP-TEA<ref name=JR />]]
-The '''Hyper Text Coffee Pot Control Protocol''' ('''HTCPCP''') is a facetious [[communication protocol]] for controlling, monitoring, and diagnosing [[coffee pot]]s. It is specified in {{IETF RFC|2324}}, published on 1 April 1998 as an [[April Fools' Day Request for Comments|April Fools' Day RFC]],<ref>{{Citation | url = http://tools.ietf.org/html/rfc2324 | title = Network Working Group | contribution = Request for Comments 2324 | publisher = [[Internet Engineering Task Force|IETF]]}}</ref> as part of an [[April Fools' Day Request for Comments|April Fools prank]].<ref>{{Cite book |last=DeNardis |first=Laura |url={{google books|plainurl=yes|id=Secqz0XQJIsC|pg=PA27}} |title=Protocol Politics: The Globalization of Internet Governance |date=30 September 2009 |publisher=MIT Press |isbn=978-0-262-04257-4 |pages=27ff |access-date=8 May 2012}}</ref> An extension, HTCPCP-TEA, was published as RFC 7168 on 1 April 2014<ref name=rfc7168>{{Citation | url = https://tools.ietf.org/html/rfc7168 | title = The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)| contribution = Request for Comments 7168 | publisher = [[Internet Engineering Task Force|IETF]]}}</ref> to support brewing teas, which is also an April Fools' Day RFC.
+The '''Hyper Text Coffee Pot Control Protocol''' ('''HTCPCP''') is a facetious [[communication protocol]] for controlling, monitoring, and diagnosing [[coffee pot]]s. It is specified in {{IETF RFC|2324}}, published on 1 April 1998 as an [[April Fools' Day Request for Comments|April Fools' Day RFC]],<ref>{{Citation | url = http://tools.ietf.org/html/rfc2324 | title = Network Working Group | contribution = Request for Comments 2324 | publisher = [[Internet Engineering Task Force|IETF]] | access-date = 2012-03-20 | archive-date = 2012-04-04 | archive-url = https://web.archive.org/web/20120404141825/http://tools.ietf.org/html/rfc2324 | url-status = live }}</ref> as part of an [[April Fools' Day Request for Comments|April Fools prank]].<ref>{{Cite book |last=DeNardis |first=Laura |url={{google books|plainurl=yes|id=Secqz0XQJIsC|pg=PA27}} |title=Protocol Politics: The Globalization of Internet Governance |date=30 September 2009 |publisher=MIT Press |isbn=978-0-262-04257-4 |pages=27ff |access-date=8 May 2012}}</ref> An extension, HTCPCP-TEA, was published as RFC 7168 on 1 April 2014<ref name=rfc7168>{{Citation | url = https://tools.ietf.org/html/rfc7168 | title = The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA) | contribution = Request for Comments 7168 | publisher = [[Internet Engineering Task Force|IETF]] | access-date = 2014-04-22 | archive-date = 2014-05-29 | archive-url = https://web.archive.org/web/20140529225719/http://tools.ietf.org/html/rfc7168 | url-status = live }}</ref> to support brewing teas, which is also an April Fools' Day RFC.
 ==Protocol==
 RFC 2324 was written by [[Larry Masinter]], who describes it as a satire, saying "This has a serious purpose &ndash; it identifies many of the ways in which [[HTTP]] has been extended inappropriately."<ref>{{Cite web |last=Masinter |first=Larry  |author-link=Larry Masinter |title=IETF RFCs |url=http://larry.masinter.net |url-status=dead |archive-url=https://web.archive.org/web/20130327202242/http://larry.masinter.net/ |archive-date=2013-03-27}}</ref> 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 [[espresso]]ly {{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,<ref>{{Citation | title = Emarsden | url = http://emarsden.chez.com/downloads/ | publisher = Chez | contribution = Emacs extension: coffee.el}}.</ref> and a number of bug reports exist complaining about [[Mozilla]]'s lack of support for the protocol.<ref>{{Citation|title=Bug 46647 – (coffeehandler) HTCPCP not supported (RFC2324)|url=https://bugzilla.mozilla.org/show_bug.cgi?id=46647|work=Bugzilla|publisher=Mozilla}}</ref> Ten years after the publication of HTCPCP, the ''Web-Controlled Coffee Consortium'' (''WC3'') published a first draft of "HTCPCP Vocabulary in [[Resource Description Framework|RDF]]"<ref>{{Citation |title=HTCPCP Vocabulary in RDF – WC3 RFC Draft |date=1 April 2008 |url=https://cstrobbe.github.io/WC3/TR/2008/RFC-htcpcp-in-rdf-20080401/ |publisher=Chief Arabica (Web-Controlled Coffee Consortium) |access-date=27 April 2017 |via=github}}</ref> in parody of the [[World Wide Web Consortium]]'s (W3C) "HTTP Vocabulary in RDF".<ref>{{Citation | editor-first = Johannes | editor-last = Koch | others = et al | url = http://www.w3.org/TR/HTTP-in-RDF/ | title = HTTP Vocabulary in RDF | publisher = [[World Wide Web Consortium|W3]] | access-date = 17 August 2009}}</ref>
+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,<ref>{{Citation | title = Emarsden | url = http://emarsden.chez.com/downloads/ | publisher = Chez | contribution = Emacs extension: coffee.el | access-date = 2009-02-10 | archive-date = 2009-02-01 | archive-url = https://web.archive.org/web/20090201001552/http://emarsden.chez.com/downloads/ | url-status = live }}.</ref> and a number of bug reports exist complaining about [[Mozilla]]'s lack of support for the protocol.<ref>{{Citation|title=Bug 46647 – (coffeehandler) HTCPCP not supported (RFC2324)|url=https://bugzilla.mozilla.org/show_bug.cgi?id=46647|work=Bugzilla|publisher=Mozilla|access-date=2005-12-21|archive-date=2011-05-14|archive-url=https://web.archive.org/web/20110514065147/https://bugzilla.mozilla.org/show_bug.cgi?id=46647|url-status=live}}</ref> Ten years after the publication of HTCPCP, the ''Web-Controlled Coffee Consortium'' (''WC3'') published a first draft of "HTCPCP Vocabulary in [[Resource Description Framework|RDF]]"<ref>{{Citation |title=HTCPCP Vocabulary in RDF – WC3 RFC Draft |date=1 April 2008 |url=https://cstrobbe.github.io/WC3/TR/2008/RFC-htcpcp-in-rdf-20080401/ |publisher=Chief Arabica (Web-Controlled Coffee Consortium) |access-date=27 April 2017 |via=github |archive-date=15 May 2021 |archive-url=https://web.archive.org/web/20210515041835/https://cstrobbe.github.io/WC3/TR/2008/RFC-htcpcp-in-rdf-20080401/ |url-status=live }}</ref> in parody of the [[World Wide Web Consortium]]'s (W3C) "HTTP Vocabulary in RDF".<ref>{{Citation | editor-first = Johannes | editor-last = Koch | others = et al | url = http://www.w3.org/TR/HTTP-in-RDF/ | title = HTTP Vocabulary in RDF | publisher = [[World Wide Web Consortium|W3]] | access-date = 17 August 2009 | archive-date = 15 October 2009 | archive-url = https://web.archive.org/web/20091015080216/http://www.w3.org/TR/HTTP-in-RDF/ | url-status = live }}</ref>
 On April 1, 2014, RFC 7168 extended HTCPCP to fully handle teapots.<ref name=rfc7168 />
@@ Line 31: / Line 31: @@
 ==Save 418 movement==
-On 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.<ref>{{Cite web |last=Nottingham |first=Mark |title=418 I'm A Teapot #14644 |url=https://github.com/nodejs/node/issues/14644#issue-248218948 |via=github}}</ref> On 6 August 2017, Nottingham requested that references to 418 "I'm a teapot" be removed from the programming language [[Go (programming language)|Go]]<ref>{{Cite web |last=Nottingham |first=Mark |title=net/http: remove support for status code 418 I'm a Teapot |url=https://github.com/golang/go/issues/21326#issue-248234750 |via=github}}</ref> and subsequently from [[Python (programming language)|Python]]'s [[Requests (software)|Requests]]<ref>{{Cite web |last=Nottingham |first=Mark |title=418 418 I'm a Teapot #4238 |url=https://github.com/requests/requests/issues/4238#issue-249497185 |via=github}}</ref> and [[ASP.NET]]'s HttpAbstractions library<ref>{{Cite web |last=Nottingham |first=Mark |title=418 I'm a Teapot #915 |url=https://github.com/aspnet/HttpAbstractions/issues/915 |via=github}}</ref> as well.
+On 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.<ref>{{Cite web |last=Nottingham |first=Mark |title=418 I'm A Teapot #14644 |url=https://github.com/nodejs/node/issues/14644#issue-248218948 |via=github |access-date=2017-08-12 |archive-date=2017-08-10 |archive-url=https://web.archive.org/web/20170810220743/https://github.com/nodejs/node/issues/14644#issue-248218948 |url-status=live }}</ref> On 6 August 2017, Nottingham requested that references to 418 "I'm a teapot" be removed from the programming language [[Go (programming language)|Go]]<ref>{{Cite web |last=Nottingham |first=Mark |title=net/http: remove support for status code 418 I'm a Teapot |url=https://github.com/golang/go/issues/21326#issue-248234750 |via=github |access-date=2017-08-12 |archive-date=2017-08-10 |archive-url=https://web.archive.org/web/20170810220643/https://github.com/golang/go/issues/21326#issue-248234750 |url-status=live }}</ref> and subsequently from [[Python (programming language)|Python]]'s [[Requests (software)|Requests]]<ref>{{Cite web |last=Nottingham |first=Mark |title=418 418 I'm a Teapot #4238 |url=https://github.com/requests/requests/issues/4238#issue-249497185 |via=github |access-date=2017-08-12 |archive-date=2021-05-15 |archive-url=https://web.archive.org/web/20210515041837/https://github.com/psf/requests/issues/4238#issue-249497185 |url-status=live }}</ref> and [[ASP.NET]]'s HttpAbstractions library<ref>{{Cite web |last=Nottingham |first=Mark |title=418 I'm a Teapot #915 |url=https://github.com/aspnet/HttpAbstractions/issues/915 |via=github |access-date=2017-08-12 |archive-date=2019-05-10 |archive-url=https://web.archive.org/web/20190510155446/https://github.com/aspnet/HttpAbstractions/issues/915 |url-status=live }}</ref> as well.
-In response, 15-year-old developer Shane Brunswick created a website, save418.com,<ref>{{Cite web |last=Brunswick |first=Shane |title=We are the teapots |url=http://save418.com |website=The Save 418 Movement}}</ref> 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]],<ref>{{Cite web |title=HTTP Error Code 418 I'm a Teapot is about to be removed from Node. We've gotta do something. [x-post /r/webdev] |url=https://www.reddit.com/r/programming/comments/6sxea0/http_error_code_418_im_a_teapot_is_about_to_be/ |via=reddit}}</ref> 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,<ref>{{Cite web |last=Nottingham |first=Mark |title=Reserving 418 |url=https://lists.w3.org/Archives/Public/ietf-http-wg/2017JulSep/0332.html |via=github}}</ref> ensuring that 418 will not be replaced by an official status code for the foreseeable future.
+In response, 15-year-old developer Shane Brunswick created a website, save418.com,<ref>{{Cite web |last=Brunswick |first=Shane |title=We are the teapots |url=http://save418.com |website=The Save 418 Movement |access-date=2021-05-15 |archive-date=2021-05-15 |archive-url=https://web.archive.org/web/20210515041851/https://save418.com/ |url-status=live }}</ref> 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]],<ref>{{Cite web |title=HTTP Error Code 418 I'm a Teapot is about to be removed from Node. We've gotta do something. [x-post /r/webdev] |url=https://www.reddit.com/r/programming/comments/6sxea0/http_error_code_418_im_a_teapot_is_about_to_be/ |via=reddit |access-date=2017-08-12 |archive-date=2017-08-11 |archive-url=https://web.archive.org/web/20170811223038/https://www.reddit.com/r/programming/comments/6sxea0/http_error_code_418_im_a_teapot_is_about_to_be/ |url-status=live }}</ref> 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,<ref>{{Cite web |last=Nottingham |first=Mark |title=Reserving 418 |url=https://lists.w3.org/Archives/Public/ietf-http-wg/2017JulSep/0332.html |via=github |access-date=2017-08-12 |archive-date=2017-08-13 |archive-url=https://web.archive.org/web/20170813012814/https://lists.w3.org/Archives/Public/ietf-http-wg/2017JulSep/0332.html |url-status=live }}</ref> 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 <code>418 IM_A_TEAPOT</code> status code.<ref>{{Cite web|date=2020-10-05|title=What’s New In Python 3.9 — Python 3.9.0 documentation|url=https://docs.python.org/3/whatsnew/3.9.html#http|access-date=2020-10-08|website=Python Documentation}}</ref> In the corresponding pull request, the Save 418 movement was directly cited in support of adoption.<ref>{{Cite web|title=Issue 39507: http library missing HTTP status code 418 "I'm a teapot" - Python tracker|url=https://bugs.python.org/issue39507#msg361134|access-date=2020-10-08|website=bugs.python.org}}</ref>
+On 5 October 2020, Python 3.9 released with an updated http library including <code>418 IM_A_TEAPOT</code> status code.<ref>{{Cite web|date=2020-10-05|title=What’s New In Python 3.9 — Python 3.9.0 documentation|url=https://docs.python.org/3/whatsnew/3.9.html#http|access-date=2020-10-08|website=Python Documentation|archive-date=2020-10-07|archive-url=https://web.archive.org/web/20201007172936/https://docs.python.org/3/whatsnew/3.9.html#http|url-status=live}}</ref> In the corresponding pull request, the Save 418 movement was directly cited in support of adoption.<ref>{{Cite web|title=Issue 39507: http library missing HTTP status code 418 "I'm a teapot" - Python tracker|url=https://bugs.python.org/issue39507#msg361134|access-date=2020-10-08|website=bugs.python.org|archive-date=2020-10-14|archive-url=https://web.archive.org/web/20201014070511/https://bugs.python.org/issue39507#msg361134|url-status=live}}</ref>
 ==See also==

v t e Internet Engineering Task Force RFC standards
Networking protocols	User Datagram Protocol (768) IPv4 (791) Transmission Control Protocol (793) Telnet (854) File Transfer Protocol (959) Domain Name System (1034, 1035) Gopher (1436) Point-to-Point Protocol (1661) Post Office Protocol (1939) Internet Message Access Protocol (3501) Network News Transfer Protocol (3977) DNSSEC (4033, etc.) Secure Shell (4251, etc.) IPsec (4301, etc.) Datagram Congestion Control Protocol (4340) Lightweight Directory Access Protocol (4510, etc.) Stream Control Transmission Protocol (4960) TLS 1.2 (5246) Network Time Protocol (5905) Hypertext Transfer Protocol (7230-7235) HTTP/2 (7540) DNS over TLS (7858, 8310) IPv6 (8200) TLS 1.3 (8446)
Data formats	Base64 (2045, etc.) Portable Network Graphics (2083) UTF-8 (3629) Uniform resource identifier (3986) iCalendar (5545) JSON (8259)
April Fools' Day RFC	IP over Avian Carriers (1149) Peg DHCP (2322) HTCPCP (2324) Evil bit (3514) UTF-9 and UTF-18 (4042) Semaphore Flag Signaling System (4824)
Category:Internet Standards

v t e Uniform Resource Identifier (URI) schemes
Official	about acct crid data file ftp geo gopher http https info ldap mailto nfs nntp sip / sips tag telnet urn view-source ws / wss xmpp
Unofficial	coffee ed2k gemini feed finger irc / irc6 / ircs ldaps magnet rsync ymsgr
Protocol list

v t e Error messages
System failure	Bomb icon Fatal system error Guru Meditation Kernel panic Linux kernel oops Red Ring of Death Sad Mac Screen of death Blue Black
Application failure	ABEND Fatal exception error Segmentation fault
Device and data errors	HTTP 402 HTTP 403 HTTP 404 HTTP 500 lp0 on fire Not a typewriter PC LOAD LETTER
Other	Abort, Retry, Fail? Bad command or file name Halt and Catch Fire HTTP 418 Out of memory
Lists	List of HTTP status codes List of FTP server return codes List of SMTP server return codes
Related	Spinning pinwheel Windows wait cursor