[zoliky]

I have a login form.
I need to store all login data in sessions. I don't want to use cookies.

The session live until browser not closed. Exist a way to add a life time for sessions? ex. The session need to live 15 minutes.

With cookies I type the following to do this:
setcookie('username', activ, time()+900);

Thanks !

[zitwep]

ITs a PHP Settings I think you can change in your php.ini

The function should be called session.cache_expire .

Correct me if I am wrong nybody

[zoliky]

i don't have access to php.ini

I need to set a session with 15 minute life.

[Nico]

This might be interesting.

http://www.captain.at/howto-php-sessions.php

[zoliky]

Thanks nico_swd, the article is good.
I have a session now with 2 minutes lifetime.

The session:

PHP Code:

$garbage_timeout = 120; // 2 minutes

ini_set('session.gc_maxlifetime', $garbage_timeout);



$cookie_path = "/";

$cookie_timeout = 120; // in seconds

session_set_cookie_params($cookie_timeout, $cookie_path);



session_start(); 

When user login to page, a session created with 2 minutes life time.
Ok.. When user click on a link after login I want to update this session time and I want to add +2 minutes.

This mean when user inactive for 2 minutes is redirected again to login page.

Thanks !

[mab]

PHP Code:

 $garbage_timeout = 120; // 2 minutes 

ini_set('session.gc_maxlifetime', $garbage_timeout); 

Setting the gc_maxlifetime to a small value does not have an effect on the functioning of your forced logout in the way you expect.

There is a common problem with this. On shared hosting and you are using the default session.save_path (on shared hosting you should set this to be within your own web space to avoid this problem) and all the session files are in one location, the shortest session.gc_maxlifetime is used. If someone else is using a longer session.cookie_lifetime and the garbage collection occurs, their session files will be deleted and they and their users will wonder why their sessions were canceled.

Note, based on direct repeatable observation, at least on Windows based PHP hosting, and I suspect on all PHP hosting, if someone is viewing a web page that is using sessions and he keeps the page open longer then the gc_maxlifetime (takes a long time to fill out a form or goes on a break) and it is a busy web server (counting all sites/domains using sessions) so that enough sessions are opened so that garbage collection occurs, the session files that are old enough will be unconditionally deleted. When this occurs the session no longer exists and anyone in the middle of a session that was deleted will receive an unexpected surprise.

Garbage collection was assumed (ASSUME = make an A**-out-of-U-and-ME) to work by only running every N sessions (N = session.gc_probability/session.gc_divisor)(despite the name probability, no randomness is involved, this is strictly a COUNTER) and it was ASSUMED that any session files older than session.gc_maxlifetime were safe to delete (there is no flagging or locking to insure that files for open sessions are not deleted. The session files are only accessed when they are created/read at the start of the session and are written to when you create a new session variable and when the session ends.) On a busy server the values for these should actually be increased.

[zoliky]

Ok, I write what I need:

I need a Session cookie: PHPSESSID with 15 minutes life time.
I use the following lines to set life for cookie:

PHP Code:

session_start();

session_set_cookie_params(900, "/"); 

900 seconds = 15 minutes.

Now, PHPSESSID live for 15 minutes. When user click on something (a link after cookie PHPSESSID exist) i want to update the PHPSESSID life and add 15 minutes again to PHPSESSID.

Please help me !
Thanks