F5 LTM appears to be overwriting the cache-control response headers

As Daniel_Wolf  mentioned it seems that this could be an issue. Also check for irules that can be doing this or if the Web acceleration profile has a setting "Ignore Headers" to none (it should be for th request headers but it could another bug)

https://support.f5.com/csp/article/K14903

Similar issue:

https://community.f5.com/t5/technical-forum/webacceleration-profile-not-caching/td-p/53618

You can test an irule as a workaround and also check the F5 bug tracker just in case:

https://support.f5.com/csp/article/K8093

Hi ,

there is a known issue, but that seems to describe the opposite of your issue: CACHE::enable failed on private/no-store content.

If you are suspecting the BIG-IP is altering the Cache-Control headers, you should take a tcpdump and compare client and server side. You can use the p interface modifier to capture client and server side traffic in one capture (K20233108: Running the tcpdump utility using the p interface modifier).

KR

Daniel