Wow! Removing the file that controlled the session array fixed the problem (suggestion 2).
I was using ssl and session data and would never have guessed it would trip things up. I would have stared at this problem for weeks and probably not have solved the problem.
Also I will change my code to include <?php instead of <? from now on just to be sure.
Thank you very much for your help. - Matthew Perry
The following is what I use - it allows caching but forces it not to be cached (it's a report, so it's changing every time). It's a little redundant, because these items are a little bit of a pain to follow. I have these running before the session is set - you may only need the session_cache_limiter call, come to think, since I'm setting these before the session starts and the others likely get overwritten.
<?php
header('Cache-Control: private, must-revalidate');
header('Pragma: private'); // allow private caching
header("Last-Modified: " . gmdate("D, d M Y H:i:s") . " GMT"); // set to be modified 'now'
session_cache_limiter("private, must-revalidate"); // allow private caching, but cache MUST check output
// rest of script
?>
Cheers,
--
- Martin Norland, Sys Admin / Database / Web Developer, International Outreach x3257
The opinion(s) contained within this email do not necessarily represent those of St. Jude Children's Research Hospital.
-- PHP Database Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
