3 ms·
I wonder if anyone has proposed a new 4xx error code for the HTTP standard that's something like "Deprecated?" Sort of like 410/Gone but actually meaning "going
by mosburger 11y ago
I wonder if anyone has proposed a new 4xx error code for the HTTP standard that's something like "Deprecated?" Sort of like 410/Gone but actually meaning "going away soon?" You could continue to return valid content in the response body but any sane client would also notice the 4xx and choke on it.
As a consumer of the API I could then (temporarily) ignore those errors and keep using the message body while I make plans to get off the platform.
EDIT: How does one go about proposing a new HTTP status code, anyway?
- xnyhps 11y agoOr just set a date and start rejecting 1% of all requests on that date, 2% the next day, etc. Software that retries immediately will get slower and slower, which will hopefully cause someone to investigate before bandwidth costs become ridiculous. Even if it doesn't help the API users to notice it, you can estimate better what it will do when you turn it off for 100% of the requests.
- nimblegorilla 11y agoAn API failing intermittently like that would be a nightmare for anyone trying to debug the situation.
- xnyhps 11y agoYou check the website to find out if they are having server problems and you see they have deprecated the API. Problem solved.
- mosburger 11y ago(Replying to my own comment) Looks like you submit proposals here: https://datatracker.ietf.org/wg/httpbis/documents/ https://datatracker.ietf.org/wg/httpbis/documents/ I'll lurk a while and learn the culture before entertaining submitting a proposal. ^_^