Rfc 8594: the Sunset HTTP Header Field (2019)
Key topics
The debate around RFC 8594, which introduced the Sunset HTTP Header Field, centers on its adoption and implementation in popular libraries like Requests and HTTPX. Some commenters, like aiven [Author], wonder why these libraries don't support the header out of the box, while others, like pimterry, point out that Requests has considered and rejected automatic handling of related deprecation headers. The discussion reveals a divide between those who see the header as a useful tool for managing API deprecations, like treve, whose REST client already logs Sunset headers, and those who criticize the terminology, such as fogzen, who finds "Sunset" to be vague marketing speak. Meanwhile, a broader conversation emerges about the challenges of implementing and discussing standards in the software development community.
Snapshot generated from the HN discussion
Discussion Activity
Light discussionFirst comment
N/A
Peak period
4
0-2h
Avg / period
2
Based on 12 loaded comments
Key moments
- 01Story posted
Aug 28, 2025 at 3:35 PM EDT
4 months ago
Step 01 - 02First comment
Aug 28, 2025 at 3:35 PM EDT
0s after posting
Step 02 - 03Peak activity
4 comments in 0-2h
Hottest window of the conversation
Step 03 - 04Latest activity
Aug 29, 2025 at 11:24 AM EDT
4 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
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.
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.
It's nice when tooling builds this sort of stuff in, because it also encourages APIs to implement it.
It explicitly doesn't have to mean deprecation, the standard says it could also be returned from any short-lived resource. There's no way to see if the header applies to the whole server or just the specific resource or even query parameters, and no way to deduplicate to ignore known warnings.
“Sunset” is marketing speak.
The Sunset HTTP Header Field - https://news.ycombinator.com/item?id=19926775 - May 2019 (82 comments)