Open Bug 1810375 Opened 2 years ago Updated 2 years ago

firefox ignores newer version of image upon reload

Categories

(Core :: Graphics: ImageLib, defect)

Firefox 108
defect

Tracking

()

People

(Reporter: p.t.deboer, Unassigned)

References

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:108.0) Gecko/20100101 Firefox/108.0

Steps to reproduce:

Setup a picture file test.png on a web server (Apache 2.4.38, essentially stock configuration on Debian).
Load this picture in two browser tabs.
Replace the picture on the server by a different one (keeping the same filename).
Press ctrl-R (or click the reload icon) in one browser tab: the picture shown updates (as expected).
Press ctrl-R (or click the reload icon) in the other browser tab: the picture shown there does NOT update.

Actual results:

See above: the two browser tabs now show different pictures for the same URL, and this persists over reloads in either tab. Only reloading with Ctrl-F5 resolves it.

I tested this with a fresh install of Firefox Nightly on Linux with a fresh profile, but the problem also exists in 108.
I've also seen cases where even the first tab in which a reload is tried does not update (despite getting a 200 response with a fresh image from the server), but I can't quite reproduce this now.

Expected results:

After reload in a tab, the current version of the picture should be displayed in that tab, regardless of what has happened in other tabs.

The Bugbug bot thinks this bug should belong to the 'Core::Graphics: ImageLib' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Graphics: ImageLib
Product: Firefox → Core
Status: UNCONFIRMED → NEW
Ever confirmed: true

Hmm, probably some artifact with root cause being bug 919113.

I think something like this: the second reload request gets a 304 unmodified response, which is sent because the image has not been modified since the first reload, and so it think it's old request from before the reloads (before the modification) is still valid and uses that.

See Also: → 919113

The severity field is not set for this bug.
:aosmond, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(aosmond)
Severity: -- → S3
Flags: needinfo?(aosmond)
You need to log in before you can comment on or make changes to this bug.