[MAGNOLIA-2011] Allow setting response headers to allow/deny cache at client side Created: 19/Jan/08  Updated: 23/Jan/13  Resolved: 01/Feb/08

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 3.5.3
Fix Version/s: 3.5.4

Type: Improvement Priority: Major
Reporter: Fabrizio Giustina Assignee: Fabrizio Giustina
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by MAGNOLIA-2037 Add the new CacheHeadersFilter to the... 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   

Actually in Magnolia there is no way to properly set cache headers (cache-control, pragma, expire...) in order to make static resource cacheable by browsers or to avoid completely cache. This can be really important in order to tweak performance and Magnolia should provide this feature by default.



 Comments   
Comment by Fabrizio Giustina [ 19/Jan/08 ]

new info.magnolia.cms.filters.CacheHeadersFilter filter committed. Documentation in javadocs

Comment by Magnolia International [ 22/Jan/08 ]

nice, thanks - we should probably add this filter to the filters chain, but disable it by default, at least until the next major release. Where in the chain would you recommend placing it?

Comment by Fabrizio Giustina [ 22/Jan/08 ]

I placed it just after activation/i18n and before cache, that's probably the best position

Comment by Magnolia International [ 22/Jan/08 ]

just reopening so we remember to add it

Comment by Magnolia International [ 01/Feb/08 ]

Will add it in the filter chain in the next release. See MAGNOLIA-2037.

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