There different issues here.
One issue is the session storage. It is associated to the cookie uuid.
This never expires unless the server side file is deleted (the script
you mention does that).
Another issue is the content of the session. For example
authentication information. That expires automatically. Even if the
session cookie is stolen it is useless.
Think of amazon. It always recognizes you but that does not mean it
always thinks you are logged in. Web2py does the same. The session
always remembers you since there is no reason to forget who you are.
That does not it always thinks you are authenticated.
The only reason to delete session server side is storage space.
On Nov 15, 12:56 pm, Richard Vézina <
ml.richard.vez...@gmail.com>
wrote:
> Hello,
>
> I just find this :
>
> Mailing-list
> [x] expire_sessions.py respects expiration time, thanks iceberg
>
> From the book :
> The file "applications/admin/cron/expire_sessions.py" actually exists and
> ships with the *admin* app. It checks for expired sessions and deletes
> them. "applications/admin/cron/crontab" runs this task hourly.
>
> I don't understand why Massimo wrote session never end up here in the
> thread?
>
> How safe it is if I adapt the expire_sessions.py to my app?
>
> What do I lost if I use to clear sessions files... Until now I was using
> them as kind of log to know what a user as do during it session.
>
> Thanks
>
> Richard
>
> On Tue, Nov 15, 2011 at 1:35 PM, Richard Vézina <
ml.richard.vez...@gmail.com