I think your problem might be very similar?

imagePlacement.src= ‘getimage.php?id=100&postNotUsed=’+Date();

Like someone else mentioned, this problem is completely random. I went through this with Firefox for several months last year, then had no problems for the last 3-4 months. Now it’s popping back up again.

I have a bunch of images which are generated automatically once a week for stats etc. These are all generated from one PHP script - showGraph.php?id=1 or showGraph.php?id=7729.

So I open Firefox and browse around on the site and go to other sites and come back and Firefox keeps using the cached version. Then I close Firefox and starts it up again. At this point instead of using the cached version, Firefox downloads the image from the server again - even though the cached version should have been used.

The headers are set as follows:

header(“Expires: Sat, 7 Oct 2006, 23:59:59 GMT”); header(“Cache-Control: public”); header(“Last-Modified: Sun, 1 Oct 2006 00:00:00 GMT”); header(“Content-type: image/png”);

Is there something I’m missing or should be doing to have Firefox use the cached copy instead of downloading an updated version after I close Firefox completely and start it up again.

I’m using FireFox 1.5.0.7 on Windows XP. Had the same issue since FireFox 1.5.0.1.

TIA

Albert

greetz andrea

Even after installing a new version of the web developer toolbar i didn’t have the problem anymore, so maybe its only caused by an older version..

It seems logical that whenever a developer passes different variables to a webpage, the content is bound to be different and the cache should not be used.

However, as bone mentioned, firefox does not use the cache even when the exact same variables are sent. This undermines a nice system to control caching but hey, if this was a perfect world I wouldn’t have anything to do ;-)

I’ve got a page where the user clicks something in a collapsable tree-view and they’re taken to another page. I’ve set up a script that restores the page to the way it was when they left it if they click “back”.

The problem? Firefox is caching the page, so the session variable that I pass back isn’t there unless I click “reload”. None of the tips from the Firefox cache page in the last comment work, only disabling the cache from the web-dev toolbar does the trick.

But on other machines around the office, the page works perfectly in Firefox. GAAAAAHHHHHHH!!!!

Oddly, it’s also firing onload when I hit ‘back’ - which contradicts all sorts of resources around the interweb. Bizarroweird.