When accessing our website through the F5 (VIP), the cache-control response headers are not honoring the values returned by the member servers in the Pool. When accessing the webservers directly (not through the F5) the cache-control header values are correct.
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).
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)