Bug ID 423805: WAM may not send Etag for content it serves from cache

Last Modified: Feb 13, 2019

Bug Tracker

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

Known Affected Versions:
11.2.0, 11.3.0, 11.4.0, 11.4.1

Fixed In:
11.5.0, 11.4.1 HF9

Opened: Jun 23, 2013
Severity: 3-Major
Related AskF5 Article:
K14737

Symptoms

When clients request compressed static content that is already in WAM cache, and the cache content needs to be revalidated, WAM may not send the etag for the content even the content has not changed on the OWS.

Impact

Without an etag sending back to the client, WAM may get unnecessary load from clients that otherwise will be able to do conditional GET with the etag.

Conditions

WAM is configured to cache compressed static content from OWS, and OWS does not send a Last-Modified date header in the response.

Workaround

Configure OWS to return the Last-Modified header for content it serves.

Fix Information

WAM now sends Etag for content it serves from cache.

Behavior Change