35163 - Image cache not refreshed on reload

Status: VERIFIED DUPLICATE of bug 30852

(Core :: Graphics: ImageLib, defect, P3)

Description

[Doron Rosenberg (IBM)]

If you view a image on your harddisk, and and then work on it and reload in
mozilla, it show's the old one, not the reworked one.

sounds like a image cache problem, could not find a similar bug in bugzilla.

seen on 2000040708.

Comment 1

[pnunn]

Thanks, I'll take a look at it.
-P

Comment 2

[R.K.Aa.]

also:
if you view a counter-image on web and hit "reload" - it reads from cache, i.e.
never changes digits. Actually this seems this happen with ALL images that are
cached - they read from cache on reload instead of from web.
Cached images are excellent when using back/forward, but reloading doesn't work
as expected: It behaves like a "back to current page" instead.

Is that considered part of this bug? If so, there's a duplicate waiting:
bug 37245

Comment 3

[Doron Rosenberg (IBM)]

*** Bug 37245 has been marked as a duplicate of this bug. ***

Comment 4

[R.K.Aa.]

This is bigger than affecting only images you see..
If you're on a modem: study RD/TD lamps while reloading a big textfile.
Almost nothing happens. The short blinks you see is a DNS lookup - and after
that cached stuff will load.
(The same DNS-lookup happens needlessly when going back/forward - that's part of
bug 32469 i think..and possibly some other ;)

Status Quo is that the reload functionality for now is just a variant of
back/forward, loading current URL instead of previous/next - images or no
images.

Worse: If preferences are set to load URL "once per session" - an URL you have
visited in an earlyer session will still load from cache if files are still
cached on disk.

Does this too fit in this bug?

I would think that depends on whether cached textfiles and images are handled
differently. I would be surprised if they are. I haven't a clue to the
mechanisms here but it would make sense if it's cached as entities of sorts..
bundles with all content included/accounted for.

Comment 5

[Doron Rosenberg (IBM)]

the idea is, if you view a image alone, not a html, a reload should cause a 
refresh of the image, not a call form cache.  That is NS4.x behaviour which is 
missing in Imagelib.  

Comment 6

[pnunn]

There are 2 different types of reload possible with using
the reload button. 'Shift-reload' is a super reload. Reload everything
from the server. Just 'reload' should not reload from the server unless
there is another factor like a pragma-nocache or a expires tag applied.

When you view an image in an html page, if the html page has not been modified
the image is not checked for modification. The top level page determines the
'freshness' for the whole page. 

When you view the image by itself, not in an html page, it IS the top level
document. 

I'll need to sit down and isolate what is going on. The problem could
be in imglib or necko.

-P

Comment 7

[R.K.Aa.]

How peculiar. The reloads should work the other way around. Normally a user
actually wants to reload from web. So the "super reload" should be the default
reload, and it should fall back to search cache if no net-connection is found. A
*local* reload, - of cached stuff only - is in my view very rarely desired. It's
already in the browser. Why should i reload it?

Comment 8

[Doron Rosenberg (IBM)]

normal reload - it causes the page to be compared, and if there has been a
change, it refreshes. That is what everyone wants, it saves bandwith, as it does
not download the entire page if there has been no change.

Super reload causes the page to be reloaded without checking if it has beed
modified, costing more bandwith if the page has not been updated.

Comment 9

[pnunn]

marking as a duplicate.
-p

*** This bug has been marked as a duplicate of 30852 ***

Comment 10

[Doron Rosenberg (IBM)]

verifying dupe.