[MGNLCACHE-147] Cache filter is not triggered for forwards Created: 23/Sep/16  Updated: 23/Nov/16  Resolved: 29/Oct/16

Status: Closed
Project: Cache Modules
Component/s: cache core
Affects Version/s: None
Fix Version/s: 5.5

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:
causality
is causing MGNLCACHE-154 Requests initiated with ERROR dispatc... Closed
dependency
is depended upon by MSITEMESH-13 Don't create a new connection for fra... 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)
Sprint: Kromeriz 64, Kromeriz 68
Story Points: 1

 Description   

The cache filter is currently triggered only once per request (it extends OncePerRequestAbstractMgnlFilter).
This is currently an issue for MSITEMESH-13 since the cache is not triggered for forwards.
Instead of extending OncePerRequestAbstractMgnlFilter, we can provide a voter which does the function so we can replace it with a custom one.



 Comments   
Comment by Roman Kovařík [ 05/Oct/16 ]

Reopened: to be reverted.
We clear the attribute which marks filter as used instead (in sitemesh).
Otherwise the same fix would be required for VariantResolverFilter.

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