[MGNLCACHE-77] Introduce mechanism for setting ttl independently from browser caching Created: 13/Oct/14  Updated: 20/Jan/15  Resolved: 11/Dec/14

Status: Closed
Project: Cache Modules
Component/s: None
Affects Version/s: None
Fix Version/s: 5.4

Type: Improvement Priority: Neutral
Reporter: Roman Kovařík Assignee: Roman Kovařík
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MGNLCACHE-76 Use constants for cache headers Closed
depends upon MGNLCACHE-81 Mark content comming from cache Closed
is depended upon by MSITEMESH-12 Allow to set TTL of a snippet 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)
Date of First Response:

 Description   

e.g. request.setAttribute("Cache-control", "ttl=0");



 Comments   
Comment by Magnolia International [ 15/Oct/14 ]

This was actually introduced for MGNLCACHE-57, which in turn impacts MGNLPN-189; those issues should be linked here, and the review should happen with that context in mind

Comment by Roman Kovařík [ 27/Oct/14 ]

Won't fix: we'll go with isCacheable voters instead, see MGNLCACHE-57.

Comment by Roman Kovařík [ 09/Dec/14 ]

We might still won't to use this if we want to influence server cache before CacheFilter is reached.
This is currently not possible because e.g.

response.setHeader("Cache-Control", "ttl=0");

is taken into account only after wrapping in CacheFilter.

Generated at Sun Feb 11 23:51:58 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.