[MGNLPN-573] Delivery content personalized via cookies or headers when using a CDN Created: 26/Aug/21 Updated: 23/Aug/22 |
|
| Status: | Open |
| Project: | Magnolia Personalization |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Story | Priority: | Neutral |
| Reporter: | Christopher Zimmermann | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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: | |
| Epic Link: | Headless p13n Backlog |
| Team: |
| Description |
|
As a marketer I want to personalize by headers and cookies even when using a CDN so that I can achieve my marketing goals with high performance. Acceptance criteria
Technical Notes Might work based on "Vary" headers https://www.fastly.com/blog/best-practices-using-vary-header Some existing related work "CDN Helper" extension. |