RFC 8594: The Sunset HTTP Header Field (2019)

16 aiven 6 8/28/2025, 7:35:22 PM datatracker.ietf.org ↗

Comments (6)

dang · 1h ago
Related. Others?

The Sunset HTTP Header Field - https://news.ycombinator.com/item?id=19926775 - May 2019 (82 comments)

aiven · 2h ago
Why do libraries such as Requests or HTTPX not support this out of the box? It would be really useful to have automatic warning or sentry event after deprecation response.

I understand that this functionality can be easily added as a plugin, but not everyone is aware that such a thing even exists. With default support, it will be easier to upgrade to new API versions and keep stuff up to date.

treve · 7m ago
My REST client emits this to console.log out of the box, and it's been really useful https://github.com/badgateway/ketting

It's nice when tooling builds this sort of stuff in, because it also encourages APIs to implement it.

pimterry · 9m ago
I suggested exactly that (for the closely related Deprecation header) to Requests a few years ago, they feel it's the application's responsibility, discussion here: https://github.com/psf/requests/issues/5724
bayindirh · 1h ago
I'll argue that if these features are more widely known and respected, we wouldn't need to re-invent these kinds of elegant solutions with clunky and thick stacks, over and over again.
AlienRobot · 1h ago
I'll argue that the major problem with everything in software is that there is no place for random developers to discuss standards they might want to implement

For example, if drag and drop and copy and paste didn't exist, it probably wouldn't be created today because you need 2 programs to agree on accepting the format (you can't even drag and drop from most software except file managers...). And even conventions that ALREADY exist are being forgotten with every year.