Mastodawn

@dyfustic Activate Hyper Text Coffee Pot Control Protocol !
#HTCPCP

Dr. Juande Santander-Vela Sep 20, 2025

Today I (re-)learned about the “418 I’m a Teapot” [1] error code, which was first codified in the April’s fools issue of Internet request for comments for 1998. RFC2324 [2] describes the Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0), and has 418 as that particular error code.

I think it might be useful, as part of the combined measures against unauthorized AI scraping, to start returning that HTTP 418 I’m a teapot error… or even mess with them with different ludicrous non-coffee things to be, such as a mate bowl, or I’m a spaceship…

After all, that’s what Internet of Things shitposting should be about, right?

/ht @osma

[1]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/418
[2]: https://www.rfc-editor.org/rfc/rfc2324

#TIL #TodayILearned #RFCs #AprilFools #AprilFoolsRFCs #HyperTextCoffeePotControlProtocol #HTCPCP

418 I'm a teapot - HTTP | MDN

The HTTP 418 I'm a teapot status response code indicates that the server refuses to brew coffee because it is, permanently, a teapot. A combined coffee/tea pot that is temporarily out of coffee should instead return 503. This error is a reference to Hyper Text Coffee Pot Control Protocol defined in April Fools' jokes in 1998 and 2014.

MDN Web Docs

Show thread

zem Mar 13, 2025

@HLunke
Hypertext Coffee Pot Control Protocol #htcpcp #RFC2324
@wtremmel

Baiyssy Oct 30, 2024

#HTCPCP #418 I'm a teapot

Jan Sep 14, 2023

#TIL that the (in)famous “418 I'm a teapot” status code was never intended for HTTP, but only for Hyper Text Coffee Pot Control Protocol (which aimed to humorously illustrate how HTTP is being abused). So the majority of libraries include this status code by mistake and getting rid of it would be a breaking change… https://www.rfc-editor.org/rfc/rfc9110.html#name-418-unused
#HTTP #HTCPCP #HTTP418 #RFC2324