Loading...
Loading...
WAM/AAM policy is configured to ignore OWS maxage header values, but the policy does not ignore the OWS Age header.
This results in WAM/AAM improperly reducing the lifetime of OWS responses by the amount of the Age header, and more frequent WAM/AAM revalidation of the affected content (possibly on every request if the Age header is larger than the policy-specified cache lifetime).
BIG-IP system with AAM provisioned, content matching a policy node not honoring OWS headers maxage and or s-maxage, and a large 'Age' value.
You can use any one of the following as a workaround: -- Honor OWS lifetime headers (s-maxage and max-age). -- Use an iRule to delete OWS Age header. -- Increase cache AAM/WAM cache lifetime for that content to compensate.
When WAM/AAM policy is configured not to honor OWS maxage, it also does not honor OWS Age headers, which is correct behavior.
Click on a version to see all relevant bugs
F5 Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.