[ryochiji]

I was wondering if anyone else was having problems with Safari caching PHP-generated pages, even when specifically told not to.

I have pages that do:

Code:
header("Expires: Mon, 26 Jul 1997 05:00:00 GMT");    // Date in the past
header("Last-Modified: " . gmdate("D, d M Y H:i:s") . " GMT"); // always modified
header("Cache-Control: no-store, no-cache, must-revalidate");  // HTTP/1.1
header("Cache-Control: post-check=0, pre-check=0", false);
header("Pragma: no-cache"); // HTTP/1.0

at the top of each page, but Safari seems to cache them anyway. Anyone else seen this? Any workarounds? Is this a known bug in Safari? TIA.

[Simon Mundy]

I think the problem is at client-side rather than server-side - changing the headers won't always work.

What I do as a quick'n'dirty workaround for situations like this is add a timestamp to a GET parameter. For example, if I have an image that needs to be constantly refreshed, I display it as:

IMG src="img.gif?id=20030317143025"

So wherever you reference your php page, just name it like so:

< a href="page.php?pid=< ?php print date() ? >" >

Does that work for you?