[MGNLADVCACHE-79] Remove mgnlCacheVariant attribute when there is no personalized cache entry Created: 01/Nov/16  Updated: 14/Nov/16  Resolved: 05/Nov/16

Status: Closed
Project: Advanced Cache
Component/s: personalization
Affects Version/s: None
Fix Version/s: 1.8.1

Type: Task 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:
dependency
is depended upon by MSITEMESH-49 Remove workarounds for MAGNOLIA-6821 ... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Sprint: Kromeriz 69
Story Points: 2

 Description   

PersonalizedCachePolicy stores mgnlCacheVariant into the request and generates the cache key according to its value.
As we now use forwards for fragment requests (MSITEMESH-13), this attributes is shared for all fragments thus might generate wrong keys for them.


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