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