[MGNLPN-238] VariantResolverFilter should only trigger for text/html (not /.magnolia and any other content type) Created: 24/Nov/15  Updated: 30/Nov/15  Resolved: 24/Nov/15

Status: Closed
Project: Magnolia Personalization
Component/s: Integration
Affects Version/s: 1.2.2
Fix Version/s: 1.2.3

Type: Task Priority: Neutral
Reporter: Philip Mundt Assignee: Philip Mundt
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
caused by MGNLPN-200 Personalization filters should trigge... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Sprint: Basel 21
Story Points: 1

 Description   

MGNLPN-200 added bypasses for info.magnolia.personalization.filter.VariantResolverFilter which are currently not working due to missing addBypass(); calls.



 Comments   
Comment by Philip Mundt [ 30/Nov/15 ]

QA has to involve testing a public instance. It has to be verified that the filter is really bypassed for /.magnolia and especially for non-text/html-requests.

Generated at Mon Feb 12 06:35:40 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.