The HTTP 418 I'm a teapot status code originates from the Hyper Text Coffee Pot Control Protocol (HTCPCP), defined in RFC 2324. The specification was published as an April Fools’ joke in 1998.
According to the RFC, the 418 response should be returned when a teapot receives a request to brew coffee.
The code was introduced as part of a humorous protocol describing how network-connected coffee machines could be controlled using HTTP-like requests.
In the fictional protocol, a teapot must refuse a request to brew coffee, because it is only capable of preparing tea. In such cases, the server responds with:
HTTP/1.1 418 I'm a teapot
Although the code was originally intended as a joke, it has become a well-known reference within developer communities.
Several platforms and web services include optional support for returning a 418 response as an Easter egg.
Despite its humorous origin, the status code became part of internet culture and is widely recognized by developers.
When the HTTP specification was revised, the code was intentionally left documented rather than removed, acknowledging its long-standing presence in developer communities.
HTTP/1.1 418 I'm a teapot Content-Type: text/plain
This response is rarely used in production systems but remains a popular cultural reference among developers.
The HTTP 418 I'm a teapot status code is a humorous addition to the HTTP ecosystem originating from an April Fools RFC. While not used in serious production environments, it has become a recognizable part of developer culture and internet history.