[MAGNOLIA-1771] cache: move deny configuration to the filter or support a per filter configuration Created: 11/Oct/07  Updated: 23/Jan/13  Resolved: 09/Jul/08

Status: Closed
Project: Magnolia
Component/s: cache
Affects Version/s: 3.1 M3
Fix Version/s: 3.6

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

Issue Links:
relation
is related to MAGNOLIA-2127 New Cache features and api 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   

The concept is that you can have multiple instance of the cache filter intance: before, after security, some parts rolebased, ...

Each of them are configured by bypasses and therefore the configuration in the cache module is redundant/obsolete



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

the CacheStrategy now takes this decision. Multiple cache filters should be supported - but to be tested.

Comment by Magnolia International [ 09/Jul/08 ]

tested and works nicely (just be careful not to have 2 filters using the same configuration, this might make the blocking cache hang...)

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