Last Modified: Apr 28, 2025
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.1, 13.1.5, 13.1.5.1
Fixed In:
14.0.0
Opened: Nov 07, 2017 Severity: 4-Minor
The max age setting on the AAM profile sets the maximum age of every document in the cache. When a client request matches a document that has exceeded the profile max age, that document is verified with the origin web server before being served to the client.
Documents with a max-age value greater than the max age setting of the profile are validated more often with the origin web server.
When a document has a max-age that is larger than the max age of the profile.
None.
The system now uses the f5-no-pma token list to tell RAM cache not to use the profile max age (pma) value to determine when to validate the document. Instead, the system uses the document's max-age, Expiration, or the HTTP heuristic value.