|
|
Posted by Dave on 05/24/05 06:05
(joealey2003@yahoo.com) decided we needed to hear...
<snip>
>
>
> My goal was a session control example.
>
> The problem i described on my first post, and it still exists on the
> lines above.
<re-quote joealey's code>...
session_cache_limiter('private');
session_cache_expire(20);
ini_set("session.gc_maxlifetime",30); // Time in seconds (1200=20min)
ini_set("session.gc_probability",100); // 100% probability
session_start();
</endquote>
>
> Try those lines with a simple count++ code to see the problem.
>
>
Its already been pointed out though that this isn't really a bug
(as per the subject), and you can't consider it PHP's fault or
"problem" either.
As I said in my earlier post, have you read the online docs about
cache limiter, esp. the user comments?
Browsers choose their own "creative" ways to interpret cache-control
headers, hence YMMV. You have to make allowances for browsers yourself
and send extra headers as needed to make things work.
--
Dave <dave@REMOVEbundook.com>
(Remove REMOVE for email address)
Navigation:
[Reply to this message]
|