News for hackers. Stuff that matters.
Re:New HTTP standards for caching on the modern web by tyingq on Thursday October 21, 2021 @06:11PM (#28951443)
It's a combination of different headers that's hard to sum up in a short comment. A good article on the subject should talk about all these headers: Expires, Cache-control, Etag, Pragma, Vary, Last-Modified

Key CDN has an article on it. They certainly would have experience and expertise there. I didn't read the whole thing, but it seems to have it covered: https://www.keycdn.com/blog/http-cache-headers

There's also some interesting exceptions where rules aren't followed. Like browsers typically have a completely separate cache for favicons. I suppose because they use the icons in funny/different ways, like bookmarks.

There are also sometimes proxies (especially corporate MITM ones) that don't follow the rules. Hence the popularity of cache-busting parameters like you described.

Re:New HTTP standards for caching on the modern web by djbusby on Thursday October 21, 2021 @09:31PM (#28952834)
I get the desired effect without Expires and Pragma, primarily using Cache-Control: no-store (or something I copied from MDN).
Re:New HTTP standards for caching on the modern web by nesarkvechnep on Friday October 22, 2021 @12:53AM (#28953865)
But no-store makes the resource uncacheable by both intermediate caches and browsers.