Notes |
|
(0002844)
|
fgaudreault
|
2012-07-19 10:21
(edited on: 2012-07-19 10:29) |
|
We should consider putting a $session->expire($time) somewhere. (redir.cgi?)
We also need to call
$session->delete()
$session->flush()
at the end of the process, somewhere in generate_release_page I guess...
|
|
|
(0002850)
|
fgaudreault
|
2012-07-25 09:54
|
|
Commited the delete/flush part for web.pm (generate_release_page).
However, we will need to see how we can fix the session handling in the CGI files. The current way is just not working. |
|
|
(0003089)
|
fgaudreault
|
2012-09-24 14:53
|
|
Bumping this to urgent. Some clients had issues recently with this. We should get rid of the cron and fix the problem once and for all. |
|
|
|
Just had this rear its ugly head. Will put in the cron workaround. Can I confirm with someone - the cron to remove the sessions after 30 mins - once registered we have a session time out of 3 days. Do I need to change that 30 min value to avoid kicking people off the system after 30 mins? Not sure what the 30 mins relates to. Is this fixed in 4? |
|
|
|
Yes it has been fixed in packetfence 4 since we use memcached to store cgi session. |
|