21–30 of 114 posts
It'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.
It'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.
If there is ever an Office Space 2, I think this is a candidate for the new fax machine.
Nice to see more members of the community discovering a classic. Also... I am so old I've seen this on the homepage multiple times :-(
Earlier quoted context omitted.
Except a 4xx error should not be issued for internal errors.
I do hope this is a humorous comment
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?)
Earlier 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?)
It'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.
>and shows ads/branding (for coffee) when it is idle. If there is ever an Office Space 2, I think this is a candidate for the new fax machine.
It’s too perfect. It could only go downhill.
I return 418 in some cases where somehow someone ended up somewhere in the code that I otherwise thought impossible. It works pretty well as far as letting folks know that something particularly unusual has happened / this isn't your ordinary error.
A less humorous unusual status code is 451. Unfortunately, it probably should be used more. https://en.wikipedia.org/wiki/HTTP_451