Forum Discussion
Daniel_Wolf
Jan 10, 2022MVP
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