Bug ID 434834: Portal Access should support conditional caching HTTP headers

Last Modified: Jun 04, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP APM(all modules)

Known Affected Versions:
11.3.0, 11.4.0, 11.4.1, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 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.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5

Opened: Oct 22, 2013
Severity: 3-Major
Related AskF5 Article:
K11773105

Symptoms

Content served with 'Last-Modified' or 'ETag' HTTP headers, and requested with 'If-Modified-Since' or 'If-None-Match' could be loaded from browser cache.

Impact

Stale page content and JavaScript errors on pages served through Portal Access after upgrade of APM.

Conditions

In the case of APM upgrade this means that browser could use content patched with old version of APM Portal Access and this leads to all kinds of compatibility issues with F5 JavaScript code.

Workaround

Remove 'If-Modified-Since' and 'If-None-Match' headers in HTTP_REQUEST event with iRule.

Fix Information

None

Behavior Change