From: Chris Shiflett <shiflett@xxxxxxx>
This is a characteristic of the caching headers that session_start()
sends. Although not directly related to your question, I think the
following article articulates this in sufficient detail:
http://shiflett.org/articles/how-to-avoid-page-has-expired-warnings
Hope that helps.
Chris
--
Chris Shiflett
http://shiflett.org/
As soon as you said caching headers, it all made sense.
Would adjusting session_cache_limiter before calling session_start maintain
the old behavior (until we redesign the application to save the user's form
field data)?
Good stuff at your link. Thanks. It helps.
_________________________________________________________________
Need a brain boost? Recharge with a stimulating game. Play now!
http://club.live.com/home.aspx?icid=club_hotmailtextlink1
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php