Loading...
Loading...
Updating of images optimized to browser-specific formats does not always cause re-caching of the non-browser-specific image.
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.
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.
None.
Before updating a cached expired browser-specific image, the cached generic image is now updated.
Click on a version to see all relevant bugs
F5 Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.