The Purge module adds a 1 year max-age option with the label '1 year (recommended for external cache invalidation)'. As described in 🐛 Design flaw? Browser won't see updated content? Active , this is bad advice since this means web browsers will also cache content for a year, and web browsers cannot be invalidated by servers. So web browsers will serve stale content until the page is explicitly refreshed.
Since we're introducing s-maxage and we're changing the label to 'Browser cache maximum age', I think we should:
Needs review
2.0
Code
A side effect of this implementation is that the extra max-age options added by the Purger module are now also available on the s-max-age fields we add, making ✨ Allow choosing more fine-grained max-ages Needs review less of an issue if the Purge module is installed.