[MGNLPN-675] Error 500 when a trait name and a cookie name matches Created: 22/Jul/22  Updated: 31/Aug/22  Resolved: 18/Aug/22

Status: Closed
Project: Magnolia Personalization
Component/s: None
Affects Version/s: 2.1.3
Fix Version/s: 3.0.0, 2.1.5

Type: Bug Priority: Neutral
Reporter: Carlos Cantalapiedra Assignee: Marek Strucka
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
Relates
relates to MGNLPN-683 Cookie Traits Cause Error For Persona... Closed
duplicate
is duplicated by MGNLPN-628 Cookie named "cookies" causes excepti... 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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Release notes required:
Yes
Epic Link: Support
Sprint: DevX 17
Story Points: 0.5
Team: DeveloperX

 Description   

Steps to reproduce

  1. Create a trait named testing.yaml
  2. Create a page with variants and associate the trait to the variant (choose Audience...)
  3. Open Google Chrome and create a cookie named testing
  4. On the pages app, try to open the variant with the testing trait associated

Expected results

The pages opens normally

Actual results

The page fails to start (error 500 is thrown)

Workaround

Use different names for cookie and for trait

Development notes

N/A


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