right now this has been sort of fixed for minimo by turning off http caching. so fixing this now would allow turning back on http caching, but not for images... the images would be stored in the image cache only...

moving minimo bugs to the new bugzilla product.

solving this bug correctly depends on being able to use the INHIBIT_CACHING load flag. once bug 232385 is fixed, we should be able to solve this bug by simply making imgLoader::LoadImage set the INHIBIT_CACHING load flag on the nsIChannel it creates.

hmm... my proposed solution would actually cause images to be cached indefinitely (i.e., until displaced by other content in the cache _or_ until replaced by an explicit page reload). this means that my proposed change could break pages that depend on being able to limit the amount of time a browser caches images. to solve this problem properly, we'd probably still need to create a HTTP cache entry containing just the meta data for the images. (the reason is that only the HTTP code knows how to properly calculate the "freshness lifetime" of a cached document.) this same problem (obviously) exists with the solution of disabling all HTTP caching.

here's the trivial patch i mentioned.

Minimo milestone 3 uses the http caching turned off solution. In milestone 4 we could explore more opitmizations.