image caching in Konqueror 4.4.5

Jerome Yuzyk jerome at
Mon Nov 8 08:20:54 GMT 2010

On Monday, November 01, 2010 05:03:00 pm RW <rwmaillists at> 
> On Mon, 1 Nov 2010 13:09:10 -0600
> Jerome Yuzyk <jerome at> wrote:
> > I always have to refresh to get the latest image, and that works.
> > It's just that opening in a new tab or window uses the old cached
> > image.
> > 
> > The sample I noted updates hourly so to test you have to wait a while
> > for a new image to be available.
> Checking may actually be causing the problem.  The file's http response
> has a Last-Modified header, but no explicit expiry header. In that
> case the time between checks on the upstream cache or origin server
> depends on how long the object has remained unchanged. By opening the
> image repeatedly you give the browser greater confidence that it's not
> going to change. Typically it's about 30% of the age, so about 20
> minutes. Refreshing typically cause the browser to check upstream
> immediately. I don't know the details of Konqueror, but that's how most
> browsers and caches work.
> It's also possible that there's been a change in your ISP's caching.

This has continued with 4.5.2. Once an image has been loaded into a new 
tab, and that tab closed, other openings in a tab (hours later) in the same 
window load the old image from the cache. The tab must be explicitly 
refreshed. Konqueror in 3.5.10 always gave me the latest image, even in a 
window that was open for weeks.

This message is from the kde mailing list.
Account management:
More info:

More information about the kde mailing list