The Deprecation HTTP response header field is used to signal to consumers of a resource (in the sense of URI) that the resource will be or has been deprecated. Additionally, the deprecation link relation can be used to link to a resource that provides additional information about planned or existing deprecation, and possibly ways in which clients can best manage deprecation.
Weak use-case.
Wrong solution (IMHO).
If one must use a header for this, how Zapier or Clearbit do it, as mentioned in appendix A.2, is the way to go.
Bloating HTTP and its implementations for REST-specific use-cases shouldn’t be generally accepted.
I have no idea what are you talking about. Setting a request/response header is not bloating HTTP. That’s like claiming that setting a field in a response body is bloating JSON.
Proper HTTP implementations in proper languages utilize header-name enums for strict checking/matching, and for performance by e.g. skipping unnecessary string allocations, not keeping known strings around, …etc. Every standard header name will have to added as a variant to such enums, and its string representation as a constant/static.
Not sure how you thought that shares equivalency with random JSON field names.
I don’t know what you are talking about.
Java provides
java.lang.Object.HttpHeaders, which is a constants class that provides static final String fields for the popular request and response headers..NET does the exact same thing with it’s
class Microsoft.Net.Http.Headers.HeaderNames.I can go on and on.
You just referenced two languages that don’t have proper sum types. lol.
Also mentioning Microsoft tech while a certain world event is taking place right now. lol.
You’re saying wrong solution but point to the right solution in the same standard?
Is your issue with the field name only? Why do you say wrong solution then?