[MAGNOLIA-2023] filters: cache should be infront of i18n Created: 25/Jan/08  Updated: 23/Jan/13  Resolved: 14/Jul/08

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 3.5.3
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:
dependency
depends upon MAGNOLIA-2246 Update CacheModuleVersionHandler Closed
relation
is related to MAGNOLIA-2058 update: cache filter can be removed d... Closed
is related to MAGNOLIA-2037 Add the new CacheHeadersFilter to the... Closed
is related to MAGNOLIA-2127 New Cache features and api Closed
is related to MAGNOLIA-2258 Remove dependency on exchange-simple/... 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   

This would make sense as we could use the current uri as the cache key instead of the original uri (which never changes)



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

done. Cache key is still based on OriginalURI, but this can now be easily changed with the new cache strategies.

Comment by Magnolia International [ 14/Jul/08 ]

For this to work properly, I had to add an (optional) dependency on exchange-simple module, because the cache filter needs to be after the activation filter. This means that currently the cache module won't sort its filters properly if the exchange-simple module is not present.

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