HTTP Status Code 418 I’m a teapot

19 APRIL 2017

I like random jokes of all sorts and this is one of my favourites. Status code 418: I’m a teapot is actually a real standard HTTP response.

418 I’m a teapot (RFC 2324) –

This code was defined in 1998 as one of the traditional IETF April Fools’ jokes, in RFC 2324, Hyper Text Coffee Pot Control Protocol, and is not expected to be implemented by actual HTTP servers. The RFC specifies this code should be returned by teapots requested to brew coffee.[48] This HTTP status is used as an Easter egg in some websites, including Google.com.[49]

See https://tools.ietf.org/html/rfc2324 for the official document.

So, I finally have a chance to implement HTTP Status Code 418: I’m a teapot with TaggunIf you send a picture of a cat (or picture that does not contain any text) to the receipt API, I will respond with Status code 418: I'm a teapot.

How appropriate!

The error code for Taggun’s receipt API not being able to transcribe a cat image, is similar to the error of teapots not able to brew coffee. I thought, how appropriate!