Would it be valid for an actual IoT teapot to return this instead of a 200 for a valid request?
HTTP Status 418 – I'm a teapot
61–70 of 114 posts
Re: HTTP Status 418 – I'm a teapot
#62Some previous discussions on this status specifically: https://hn.algolia.com/?q=418 Some fun ones: - Discussion on the status itself: https://news.ycombinator.com/item?id=24206899 - NPM proxy users receiving ERR 418 I'm a teapot: https://news.ycombinator.com/item?id=17175960 - Reserve the 418 status code: https://news.ycombinator.com/item?id=15004907
The NPM one is fun now, but man that was a frustrating one when it was happening. Explaining to people I couldn’t deploy the app because NPM decided it was a teapot. Error messages do not need to be silly.
I remember I was at some training course for New Relic and we zoned out when the alert came through. Having come across 418 before, I recognised it in our failed build pipeline and facepalmed. My coworker asked how do we fix it and U said I honestly don't know because it's never actually meant to be a real error code but here we are!
Re: HTTP Status 418 – I'm a teapot
#63It's quaint, it's a joke about IoT devices before they were everywhere. I'm currently disappointed that the office has "upgraded" coffee machines and the new one has a permanent internet connection and shows ads/branding (for coffee) when it is idle.
Yo dawg.... We heard U like coffee
Re: HTTP Status 418 – I'm a teapot
#64Earlier quoted context omitted.
I do hope this is a humorous comment
Why? The codes mean things, 418 specifically is a joke, but the entire 4xx range are client errors, i.e. a differently formed request would've succeeded. A perhaps-reasonable suggestion could be to use a 5xx range code that isn't specified. E.g. 555, or 567. (But I'm not sure how it would ever not simply be a 500 - server thought it couldn't happen, it could and did, that's just a plain and simple error isn't it?)
I think the idea behind 418, as much as there was an idea beyond a joke, was to indicate you sent your request to a teapot instead of a server. So yeah, client error for why it's not 518 instead.
But it works in this example for "client did something weird I don't understand", so still client error - something akin to a 404, "client tried to go somewhere I don't understand".
Re: HTTP Status 418 – I'm a teapot
#65Would it be valid for an actual IoT teapot to return this instead of a 200 for a valid request?
It's an error code. It should be returned by a tea pot as a response to a request for coffee.
Re: HTTP Status 418 – I'm a teapot
#66I really hope this is used by https://cosori.com/products/smart-electric-gooseneck-kettle-...
Re: HTTP Status 418 – I'm a teapot
#67Earlier quoted context omitted.
Why? The codes mean things, 418 specifically is a joke, but the entire 4xx range are client errors, i.e. a differently formed request would've succeeded. A perhaps-reasonable suggestion could be to use a 5xx range code that isn't specified. E.g. 555, or 567. (But I'm not sure how it would ever not simply be a 500 - server thought it couldn't happen, it could and did, that's just a plain and simple error isn't it?)
I think the idea behind 418, as much as there was an idea beyond a joke, was to indicate you sent your request to a teapot instead of a server. So yeah, client error for why it's not 518 instead. But it works in this example for "client did something weird I don't understand", so still client error - something akin to a 404, "client tried to go somewhere I don't understand".
Yes, exactly, I wasn't excluding 418 in saying all 4xx are errors in the client's request.
But 'client did something weird I don't understand' is a 400, 405, something; not the same as 'this cannot happen' at all.
Re: HTTP Status 418 – I'm a teapot
#68It's quaint, it's a joke about IoT devices before they were everywhere. I'm currently disappointed that the office has "upgraded" coffee machines and the new one has a permanent internet connection and shows ads/branding (for coffee) when it is idle.
Sounds like it needs to be playing Doom instead. Or hacked to show branding for tea.
Re: HTTP Status 418 – I'm a teapot
#69Earlier quoted context omitted.
I think for the same reason that Fawlty Towers ended after one season, there should never be a sequel to Office Space. It’s too perfect. It could only go downhill.
No, there must be a sequel; Open Office Space. Office Space is great but the cubicles date it firmly in the 90s.
Office Space 2 => Open Office Space => Silicon Valley