Bug ID 459195: Image optimization inconsistent

Last Modified: Apr 10, 2019

Bug Tracker

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

Known Affected Versions:
11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9

Fixed In:
11.6.0

Opened: Apr 25, 2014
Severity: 4-Minor

Symptoms

Updating of images optimized to browser-specific formats does not always cause re-caching of the non-browser-specific image.

Impact

An image which changed twice on OWS might be cached one way in browser-specific format and another in generic format if client requests for the generic image are so infrequent that the image has changed on OWS between requesting the two formats.

Conditions

If an image changes on OWS and has expired in cache and is only requested/served in "optimized for client" format (WebP or jpegxr) the cached jpeg is not updated until subsequently requested.

Workaround

None.

Fix Information

Before updating a cached expired browser-specific image, the cached generic image is now updated.

Behavior Change