I learned about this http response code too late. About 4 years ago I was working at a startup and I was the "lead engineer" (aka only engineer) on a project where I had to design and implement an entire REST API. I really wish I would have put this in somewhere, since we weren't doing code review (because it was literally only me).
Bit disappointed that this is not built into the c# http status codes. Was building a mock service and wanted to return something that would never occur in production for things I didn't have definitions for. This seemed like a perfect response but it's not part of the statues enum.
25 Comments
akariii@lemmy.blahaj.zone · 40 pts · 3y
teapot. its used when the server refuses to brew coffee for the client because it's a teapot, not a coffee pot
Kolossos@lemmy.world · 26 pts · 3y
See https://www.rfc-editor.org/rfc/rfc2324 and https://www.rfc-editor.org/rfc/rfc7168. Then take a look at the dates the RFCs were published :)
owenfromcanada@lemmy.world · 9 pts · 3y
Haven't read through that in a long time. Still hoping to get a HTCPCP-compliant coffee pot some day.
Randy_Bobandy@lemmy.ml · 14 pts · 3y
inspxtr@lemmy.world · 7 pts · 3y
lol what’s the context here?
Zeus@lemmy.world · 20 pts · 3y
it's a
n officialhttp response codeedit: no it's not
Dandroid@lemmy.world · 8 pts · 3y
I learned about this http response code too late. About 4 years ago I was working at a startup and I was the "lead engineer" (aka only engineer) on a project where I had to design and implement an entire REST API. I really wish I would have put this in somewhere, since we weren't doing code review (because it was literally only me).
sedawk@sh.itjust.works · 2 pts · 3y
Definitely GET /
original_ish_name@latte.isnot.coffee · 6 pts · 3y
*unofficial but may as well be official at this point
Zeus@lemmy.world · 1 pts · 3y
oh wow you're right. i've seen it in "official-ish" sites so often, but never read the actual rfc docs and it's just "unused"
spike@discuss.tchncs.de · 2 pts · 3y
It's a HTCPCP Response Code.
waspentalive@lemmy.one · 6 pts · 3y
It is what your internet connected Tea kettle responds with when receiving a coffee information request.
MajinBlayze@lemmy.world · 5 pts · 3y
Joke built into the http standard
Yorokobii@lemmy.fmhy.ml · 6 pts · 3y
looks like a brodie enjoyer to me~
sorrybookbroke@sh.itjust.works · 6 pts · 3y
The first RFC I've enjoyed reading https://www.rfc-editor.org/rfc/rfc2324#section-2.3.2
darknavi@vlemmy.net · 5 pts · 3y
Teapot. Can't you
pour tearead?cupcakezealot@lemmy.blahaj.zone · 4 pts · 3y
This is just step one of the British path to world programmer domination. Next up. All references to color will now be spelled in the proper colour
saluki@discuss.tchncs.de · 1 pts · 3y
How did you find out about this? It was meant to be top secret.
epyon22@sh.itjust.works · 4 pts · 3y
Bit disappointed that this is not built into the c# http status codes. Was building a mock service and wanted to return something that would never occur in production for things I didn't have definitions for. This seemed like a perfect response but it's not part of the statues enum.
meekah@lemmy.world · 3 pts · 3y
what stops you from just passing a 418
int?enumsare just fancyintsin c#camelCaseGuy@lemmy.world · 1 pts · 3y
I've used this one in prod a couple of times. Only for internal services and in a very well defined situation. But it's great to be able to use it.
betterdeadthanreddit@lemmy.world · 1 pts · 3y
https://github.com/joho/7XX-rfc Some additional status codes to cover a wide variety of interesting situations.