If you are referring to the "Cache-Control: maxage=x, s-maxage=x" HTTP headers, by _default_ the BigIP won't touch any of these. There are three exceptions:
1. You have WebAccelerator configured on the VIP,
2. You have an iRule either changing or removing the header from the response, or
3. You have RAM caching on in the HTTP profile configured on the VIP and it is ignoring the maxage and no-cache headers to store a local copy in memory.
In the last case, it won't _alter_ the maxage header, but depending on how its configured it may cache data beyond the maxage value.
If you're not referring to Cache-Control, then the message above applies. :>