It looks it would not cause too short expiration of session. (Expire is not set
for cookie. This is not what you want probably, but this should not cause
expiration of cookie within 10 or 20 min. You changes session.cache_expire, but
set Expire: and no cache headers. I think you don't need to do
> Then how about check the server's response headers that sent to client? You
> can view headers using wget or like. PHP might be sending global ini
> var(which is set to small number) to client for some reason.
Ok, this is the header information I get.
HTTP/1.1 200 OK
Date: Thu, 08 Mar 2001 11
> On Thursday 08 March 2001 11:14, Yasuo Ohgaki wrote:
> > I guess your clients PC's clock is not accurate. How about set timeout
to
> > 0? Then session cookie will not timeout until browser is closed.
>
> Actually the server and client clock only differs with about 1 minute.
Then how about check
On Thursday 08 March 2001 11:14, Yasuo Ohgaki wrote:
> I guess your clients PC's clock is not accurate. How about set timeout to
> 0? Then session cookie will not timeout until browser is closed.
Actually the server and client clock only differs with about 1 minute.
The 0 timeout will not work.
I guess your clients PC's clock is not accurate. How about set timeout to 0?
Then session cookie will not timeout until browser is closed.
You can compile PHP with trans-sid to add session id automatically.
http://www.php.net/manual/en/ref.session.php
I've posted PHP session helper HTML file tha
Hi all,
I have a timeout problem with sessions. I use the PHP session handling
(4.0.4pl1). It works, but it times to fast out.
I've set:
ini_alter("session.gc_maxlifetime", "172800");
and
phpinfo() says:
session.cache_expire: local=172800, global=180
session.gc_maxlifetime: local=172800, glo
6 matches
Mail list logo