[MAGNOLIA-3420] browser cache policy: allow fine grained configuration, better default settings Created: 28/Nov/10  Updated: 20/Feb/15  Resolved: 29/Nov/10

Status: Closed
Project: Magnolia
Component/s: cache
Affects Version/s: None
Fix Version/s: 4.4

Type: Improvement Priority: Major
Reporter: Philipp Bärfuss Assignee: Philipp Bärfuss
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
is causing MAGNOLIA-3426 New browser cache configuration is to... Closed
relation
is related to MGNLSTK-716 make theme images cachable in the bro... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)

 Description   

The browser cache policy configuration is rather dumb. It just takes a single expiration values for all cache entries.

A better configuration for browser caching is:

  • dont' cache HTML file (in case user names or similar are shown)
  • allow caching of js/css files
  • allow caching of files in mgnl-resources
  • support the *.md5.cache.ext pattern for far future caching

Generated at Mon Feb 12 03:46:18 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.