It currently is quite painful to have to setup two different instances to manage a load-balancer and a CDN distribution. Web assets protected behind F5XC’s load-balancers should be given the option to be cached by the load-balancer.

The setting would be just a drop-down menu offering to cache either:

• cache all the responses

• cache a set of responses specified by extensions/regexes (.css, .html,...)

• cache depending on the headers returned with the response