6 ms·
For those who may not know, this comes from RFC 2324: ""Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0), The RFC was published 1 April 1998 (April Fool's Da
by daveslash 5y ago
For those who may not know, this comes from RFC 2324: ""Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0), The RFC was published 1 April 1998 (April Fool's Day). There's a long history of humorous RFCs published on 1 April. For example, RFC 1149 "IP over Avian Carriers" https://en.wikipedia.org/wiki/IP_over_Avian_Carriers https://en.wikipedia.org/wiki/IP_over_Avian_Carriers
List of Additional April Fool's RFCs https://en.wikipedia.org/wiki/April_Fools%27_Day_Request_for_Comments https://en.wikipedia.org/wiki/April_Fools%27_Day_Request_for...
- Teknoman117 5y agoI still love that people actually went through the effort to "implement" it.
- mzzter 5y agoAny links to APIs that implement a 418 HTTP response code?
- lodovic 5y ago.Net seems to have it: https://docs.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.http.statuscodes.status418imateapot?view=aspnetcore-5.0 https://docs.microsoft.com/en-us/dotnet/api/microsoft.aspnet...
- jamespwilliams 5y agohttp.StatusTeapot in Go: https://pkg.go.dev/net/http#pkg-constants https://pkg.go.dev/net/http#pkg-constants 4k+ results on Github: https://github.com/search?utf8=&q=http.StatusTeapot&type=Code; https://github.com/search?utf8=&q=http.StatusTeapot&type=Cod... ~600 excluding _test.go files: https://github.com/search?q=http.StatusTeapot+-filename%3A*_test.go&type=Code https://github.com/search?q=http.StatusTeapot+-filename%3A*_...
- deleted 5y ago[deleted]
- madamelic 5y agoIf I have anything to do with it, there is a 418 response hidden somewhere. I recall a few internal projects at a previous employer would return 418 if the user managed to royally mess something up as a "wtf, how are you here?!" kind of response. I feel like I am not alone in implementing 'weird' HTTP codes when I get bored / as an easter egg. Pretty sure I also used HTTP 420 at least once.
- flatiron 5y ago“Uhh ummm no” -code reviewer
- codr7 5y agoYeah, code reviews definitely killed some of the fun in coding, they are rarely performed with humor.
- rockwotj 5y agoI generally make it a goal to have a test case with silly enough data to get a comment from a reviewer.
- KineticLensman 5y agoI remember reviewing a really long document (> 50 pages) that had in one bullet list the phrase 'Marks and Spencer tandoori chicken sandwich'. The doc was otherwise camera ready and the phrase was obviously there to see if I was in fact reading it
- deleted 5y ago[deleted]
- jylauril 5y agoAh, the good ol' 420 - EnhanceYourCalm
- deleted 5y ago
- tbronchain 5y agoBinance API (i.e https://api.binance.com/api/v3/ticker/price https://api.binance.com/api/v3/ticker/price) does it when there are too many requests from one IP (I assume that's the reason). They could have used something else like 429 but for some obscur reasons they're using 418 (if anyone knows the actual reason...). It will happen often if you try to make a call to their API through Google sheet scripts.
- darkhorn 5y agohttps://www.google.com/teapot https://www.google.com/teapot
- pkd 5y agoNo link but our internal API for mobile apps returns a 418 if the installed version is too old.
- lallysingh 5y agoIf you have an IoT teapot, when do you return it?
- TobTobXX 5y agoFrom the docs: > ... indicates that the server refuses to brew coffee because it is, permanently, a teapot. So I guess, when it is asked to perform coffee brewing? But pay close attention, to your general purpose brewer: > A combined coffee/tea pot that is temporarily out of coffee should instead return 503.
- spc476 5y agoI added the 418 response code to my gopher server [1]. There was one web bot that constantly hit it and was clueless that it wasn't a web server. It finally got a clue. [1] https://github.com/spc476/port70 https://github.com/spc476/port70
- claviska 5y agoI sometimes return a 418 when request heuristics detect bad behavior that looks intentional. I don’t document it, though.
- atoav 5y agoHttp.cat implements it: https://http.cat/418 https://http.cat/418
- SilasX 5y agoTo toot my own horn, I did an April Fool’s status code RFC: 397 Tolerating, for when a client sends a flawed request, but you’re going to tolerate it because you know what they really meant: https://pastebin.com/TPj9RwuZ https://pastebin.com/TPj9RwuZ
- xwdv 5y agoThis is a good idea for APIs that allow you to update an object by sending a partial JSON object with the keys you want to update, when technically you’re supposed to send the entire updated object representation unless JSON Patch is being used.
- munk-a 5y agoAlternatively there actually is a HTTP PATCH verb that you can use for this - I think that tolerating is more appropriate for common misspellinks - i.e. accepting a request like an HTTP POST {"days": 12, "horus": 13 "minutes": 27}
- jfrunyon 5y agoApril Fools RFCs are part of the "Independent Stream", which mean the top left would say "Independent Submission", not IETF. Also, Informational, not Standards Track. Just FYI :)
- eyelidlessness 5y agoIs this basically "I'm doing the robustness principle but also communicating that I'm judging you"?
- Handytinge 5y agoI'm shocked nobody's posted it yet, but iiNet (Australian ISP)'s coffee cam[0] is 13+ years running now: https://coffeecam.iinet.net.au/coffee/ https://coffeecam.iinet.net.au/coffee/