Bug ID 498302: Wrong Last-Modified Date on Cached, Refreshed Objects

Last Modified: Sep 13, 2023

Affected Product(s):
BIG-IP AAM(all modules)

Known Affected Versions:
12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2

Fixed In:

Opened: Dec 23, 2014

Severity: 4-Minor


If the BIG-IP has cached an object, the lifetime of that object has expired, and a new request for that object comes in, the BIG-IP will perform a conditional GET to the web server to determine if the object has changed. If the object has changed, the new object will be read from the web server and returned to the client, but with the cached Last-Modified time stamp instead of the new Last-Modified time stamp.


Possible cache incoherency, especially if down stream caches or client web browsers used the Last-Modified time stamp to determine the freshness of their cached content.


As above.



Fix Information

The new object will now be served to the client with the new Last-Modified time stamp.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips