teapot. its used when the server refuses to brew coffee for the client because it’s a teapot, not a coffee pot
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 :)
The “data” for most coffee URIs contain no caffeine.
Haven’t read through that in a long time. Still hoping to get a HTCPCP-compliant coffee pot some day.
Here is my handle, here is my censored
looks like a brodie enjoyer to me~
lol what’s the context here?
it’s an official http response code
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).
Definitely GET /
*unofficial but may as well be official at this point
It is what your internet connected Tea kettle responds with when receiving a coffee information request.
Joke built into the http standard
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
How did you find out about this? It was meant to be top secret.
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.
The first RFC I’ve enjoyed reading https://www.rfc-editor.org/rfc/rfc2324#section-2.3.2
Teapot. Can’t you ~pour tea~ read?
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.
Every time I write a unit test that involves a (mocked) request, and it doesn’t matter what status I use, I use this one.
