IETF Draft Proposes HTTP 483: "I'm Not a Freezer"
The Hypertext Transfer Protocol Status Code 483 (I'm Not a Freezer)
An independent Internet-Draft by R. Bánffy defines HTTP status code 483 (I'm Not a Freezer), returned when a server understands a request requiring freezing or refrigeration but cannot provide it. The document insists a server must not claim 483 just because it runs cold, uses liquid cooling, offers "cold storage," or has frozen processes or a frosty hostname. It also separates freezers from refrigerators and positions 483 alongside the teapot's 418.
This document does not allocate a separate status code meaning "I'm Only a Refrigerator". Such allocation is left for future work, preferably after an appropriate cooling-off period.
- InvisibleUp
If taken as an actual HTTP code, this has significant overlap with 422 (Unprocessable Content) and HTTP 501 (Not Implemented).
- r4ndomname
This is something I’ve been thinking about for a long time, particularly in the context of critical infrastructure providers such as hospitals. However, I always got stuck on the fact that anyone could return such a status code to deter attackers, which would ultimately render the indicator meaningless.
- russfink
Might not be a freezer, but the Intro is AI, according to Pangram.
- throw-the-towel
This is an anti-pattern. A better, future-proof solution would be to extend HTTP 418 with a header stating just what the server is not:
HTTP 418 I'm A Teapot
I'm-Not-A: freezer;teapot;radio
- gliptic
This is nonsensical so I'm thinking LLM generated.
> A server MUST NOT return 483 merely because:
> * its operating temperature is below ambient temperature;
Why would it return `I'm Not a Freezer` because it's cold?