Reserving the 418 HTTP Status Code
mnot@mnot.net
https://www.mnot.net/
General
httpbis
Internet-Draft
was an April 1 RFC that lampooned the various ways HTTP was abused; one such abuse was the definition of the application-specific 418 (I’m a Teapot) status code.
In the intervening years, this status code has been widely implemented as an “easter egg”, and therefore is effectively consumed by this use.
This document changes 418 to the status of “Reserved” in the IANA HTTP Status Code registry to reflect that.
RFC EDITOR: please remove this section before publication
The issues list for this draft can be found at https://github.com/mnot/I-D/labels/thanks-larry.
The most recent (often, unpublished) draft is at https://mnot.github.io/I-D/thanks-larry/.
Recent changes are listed at https://github.com/mnot/I-D/commits/gh-pages/thanks-larry.
See also the draft’s current status in the IETF datatracker, at
https://datatracker.ietf.org/doc/draft-nottingham-thanks-larry/.
was an April 1 RFC that lampooned the various ways HTTP was abused; one such abuse was the definition of the application-specific 418 (I’m a Teapot) status code.
In the intervening years, this status code has been widely implemented as an “Easter Egg”, and therefore is effectively consumed by this use.
This document changes 418 to the status of “Reserved” in the IANA HTTP Status Code registry to reflect that.
This indicates that the status code cannot be assigned to other applications currently. If future circumstances require its use (e.g., exhaustion of all other 4NN status codes), it can be re-assigned to another use.
Implementations are encouraged to avoid “squatting” on status codes in this manner; while there are a number of unassigned status codes in each range currently, unofficial, uncoordinated use makes the definition of new status codes more difficult over the lifetime of HTTP, which (hopefully) is a potentially very long period of time.
This document updates the following entry in the Hypertext Transfer Protocol (HTTP) Status Code Registry:
Value: 418
Description: Reserved
Reference: [this document]
IANA should also typographically distinguish “Unassigned” and “Reserved” in the registry descriptions, to prevent confusion.
This document has no security content.
Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0)
This document describes HTCPCP, a protocol for controlling, monitoring, and diagnosing coffee pots. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.