[MAGNOLIA-2037] Add the new CacheHeadersFilter to the default filter chain Created: 01/Feb/08  Updated: 11/Jul/08  Resolved: 11/Jul/08

Status: Closed
Project: Magnolia
Component/s: cache, core
Affects Version/s: None
Fix Version/s: 3.6

Type: Task Priority: Major
Reporter: Magnolia International Assignee: Magnolia International
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MAGNOLIA-2011 Allow setting response headers to all... Closed
relation
is related to MAGNOLIA-2058 update: cache filter can be removed d... Closed
is related to MAGNOLIA-2127 New Cache features and api Closed
is related to MAGNOLIA-2023 filters: cache should be infront of i18n Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty

 Description   

Fabrizio commited this new filter with MAGNOLIA-2011. We should add it to the filter chain (maybe disabled by default)
It probably belongs to the cache module, too. Or to its own module.



 Comments   
Comment by Magnolia International [ 05/May/08 ]

Will move this new filter to magnolia-module-cache

Comment by Magnolia International [ 27/Jun/08 ]

There is now the SetExpirationHeaders CachePolicyExecutor which does this and is configured in the default executors.
The filter is still present so one can add it manually if needed or if not using the cache filter or its default executors.
Note that its been moved to the info.magnolia.module.cache.filter package. The one in magnolia-core is still present but has been deprecated and will be removed in future versions.

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