News for hackers. Stuff that matters.
Re:The Sunset HTTP Header Field by politelemon on Thursday May 16, 2019 @07:10AM (#19927860)
I am not sure if Sunset is the best term here. Sunsetting in such a context would indicate retirement:

https://en.wikipedia.org/wiki/Application_retirement

However the example given is indicative of a session duration, not a sunset period.

> For example, a pending shopping order represented by a resource may already list all order details, but it may only exist for a limited time unless it is confirmed and only then becomes an acknowledged shopping order.

Admittedly, naming things is hard, perhaps this could have been called Expiry: or Unavailable-After: or Valid-Until:

Re:The Sunset HTTP Header Field by combatentropy on Thursday May 16, 2019 @10:32PM (#19935711)
I hate Sunset too, albeit for a different reason. It's businessese, like Legacy, Utilize, and for that matter, Retire (in this sense).

Choose the word that is old, short, and plain. Sunset is a little better than others because at least it is poetic. But for my HTTP headers I would prefer something a little more straightforward, rather than euphemistic --- like Expires, but that's already taken.

Re:The Sunset HTTP Header Field by shakna on Thursday May 16, 2019 @09:12AM (#19928672)
Well, we already have Expires for marking responses as stale in cache, and it's also takes just a date string, so things could get confusing there.
Re:The Sunset HTTP Header Field by politelemon on Thursday May 16, 2019 @11:22AM (#19929842)
Perhaps we could Sunset the Expires header first...
Re:The Sunset HTTP Header Field by rpc3 on Thursday May 16, 2019 @07:14AM (#19927888)
My impression was the shopping example would be more aligned with something like delivery info -- it's not there just for a session, but a month after the package is marked "delivered" it's probably at least marked for deletion.

(To be fair, I'm not sure announcing that kind of mid-term expiry is a real need-to-be-filled in today's web.)