——————————————————————
[ IETF PROTOCOL RECEIPT ]
[ RFC: 2324 | STATUS: 418 ]
——————————————————————
ID: @rusty__shackleford
AGENT: HTCPCP/1.0 (TEAPOT)
——————————————————————
[!] REQUEST: POST /BREW_COFFEE
[!] RESPONSE: 418 I'M A TEAPOT
——————————————————————
– ENTITY: SHORT & STOUT
– HANDLE: ATTACHED
– SPOUT: PRESENT
——————————————————————
RESULT: REQUEST TOTALLY REJECTED
REASON: ARCHITECTURAL LIMITATION
——————————————————————

#developerHumor #techHumor #http418 #http #networking #ImATeapot

I had a little bit of extra time when making our health endpoint. Added these two fun little features.
#HTTP418 #ImATeapot
#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

The HTTP status code I never knew about 😉 😎

"418 I'm a teapot"

https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/418

#devops #webdeveloper #http418 #tgif

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

lol, i totally didn't know that Google has a error 418 teapot demo, this is amazing 🤣​.

#Google #418teapot #error418 #http418