Skip to main content

Reserving the 418 HTTP Status Code
draft-nottingham-thanks-larry-00

Document Type Replaced Internet-Draft (individual)
Author Mark Nottingham
Last updated 2018-04-19 (Latest revision 2017-08-11)
Replaced by RFC 9110
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-httpbis-semantics
Telechat date (None)
Responsible AD (None)
Send notices to (None)
This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at:
https://www.ietf.org/archive/id/draft-nottingham-thanks-larry-00.txt

Abstract

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

Authors

Mark Nottingham

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)