418 I'm a teapot: The Famous April Fools' Joke

The Story Behind 418

On April 1, 1998, Larry Masinter and the HTTP Working Group published RFC 2324 as an April Fools' joke. The RFC defined the "Hyper Text Coffee Pot Control Protocol" (HTCPCP), a protocol for controlling coffee pots. The 418 status code was included to indicate that the server is a teapot and cannot brew coffee — a reference to the classic "Teapot" joke from the IETF.

Despite being a joke, 418 was officially registered by IANA and remains in the registry to this day. Many developers are aware of it, and some frameworks include it as a fun easter egg:

• Node.js (Express): res.status(418).send('I\'m a teapot');
• Python (Flask): return 'I\'m a teapot', 418
• Ruby on Rails: render status: 418, plain: "I'm a teapot"
• Spring Boot: HttpStatus.I_AM_A_TEAPOT

What the RFC Says

From RFC 2324 (Section 2.3.2):

Yes, the RFC includes the "short and stout" pun from the nursery rhyme.

Is 418 a Real Status Code?

• Officially registered – yes, IANA lists it.
• Supported by frameworks – many HTTP libraries include it.
• Never used in production – you should not return 418 in a real application.
• Used for fun – sometimes included in APIs as an easter egg (e.g., returning 418 on April 1).

When to Use 418

• Never in production – it will confuse users and developers.
• For testing – it can be used as a fun way to check if your client handles unknown status codes.
• As an easter egg – on April 1st, some APIs return 418 for a laugh.
• For educational purposes – to demonstrate that HTTP has a sense of humor.

Fun Fact

Google's I/O conference in 2014 included a "Teapot" reference: a QR code on a teapot that returned a 418 status when scanned. Some Go libraries also include 418 as a known status code.