![]() in that "Any attempt to brew coffee with a teapot should result in the HTTP error code 418 I'm a teapot and the resulting entity body MAY be short and stout". ![]() ![]() (.) Now, you may be asking, if this is a COFFEE protocol, why the "teapot" code? This is answered in Section 2.3.2. Now, the RFC is pretty funny with lines like "Coffee pots heat water using electronic mechanisms, so there is no fire. This was a brand new protocol for controlling, monitoring, and diagnosing coffee pots. Every year since 1989, they release a few humorous RFC’s for April’s Fool Day and on April 1st, 1998, RFC 2324 introduced the "Hyper Text Coffee Pot Control Protocol" or (HTCPCP/1.0). To propose new standards, the members release RFC’s or "Requests for Comments" to the community. "So, what’s the "418 I'm a teapot" all about? Well, the group of people who make these codes and set the standards is the IETF or "Internet Engineering Task Force". Most of you devs may already known this staus code and even its history, but many dont. This error is a reference to Hyper Text Coffee Pot Control Protocol which was an April Fools' joke in 1998. The HTTP 418 I'm a teapot client error response code indicates that the server refuses to brew coffee because it is a teapot. ![]() The server refuses the attempt to brew coffee with a teapot. I was building an API, and consulting some http status codes when i saw the 418 status code on the MDN documentation. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |