[MAGNOLIA-3297] browser caching: make it configurable, support far future caching Created: 10/Sep/10  Updated: 29/Jan/13  Resolved: 24/May/11

Status: Closed
Project: Magnolia
Component/s: None
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:
relation
is related to MGNLCACHE-4 Items with .cache. in their url shoul... Closed
is related to MGNLSTK-786 far future cache: use a more resource... 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 is currently very limited. It should take its own voters and should support different time settings to allow far future caching of resources which will never change (they have a md5 or version number in the filename.



 Comments   
Comment by Philipp Bärfuss [ 24/May/11 ]

As of Magnolia 4.4 we are supporting far future caching if configured so. We use this feature for instance in MGNLSTK-714.

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