[ABTEST-382] CDN. Research caching integration Created: 17/Dec/20  Updated: 10/Nov/22

Status: Open
Project: A/B Testing
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: New Feature Priority: Neutral
Reporter: Andrei Ichimescu Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Screenshot 2022-11-10 at 09.31.44.png     PNG File Screenshot 2022-11-10 at 09.36.32.png    
Issue Links:
Relates
relates to ABTEST-430 Include a X-Header in the HTTP respon... Closed
Template:
Acceptance criteria:
Empty
Date of First Response:
Epic Link: ABn Later
Team: AuthorX

 Description   

 
How can we apply caching to a running test?
 
One question came up from the Deutsche Bahn demo on ABn-testing, regarding Caching on a CDN: 
Does Magnolia in any way signal that an A/B test is active in the HTTP response headers? So that our CDN could decide whether it can cache the page or not.
 

Goal - minimize impact going to the public instance
 This use case is now even more relevant for SaaS customers; and it applies to both ABn Testing variants, but also to Personalisation variants. The solution would solve issues where the client doesn't want to send traffic to the public, due to sheer the volume of users that needs to go through CDN & Load balancer 



 Comments   
Comment by Michael Duerig [ 29/Mar/21 ]

As discussed today in the GA readiness prep call, we will not implement full support for CDN for GA. However we investigate whether we can set a specific X-Header on pages that are part of a test. This way CDNs can be configured to at least ignore such pages allowing test testing to go forward.

Generated at Sun Feb 11 22:55:41 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.