Yes, it does generate new session_id. The user has essentially told Django to expire the session, which in turn results in a new session key.
I'm starting to agree with Malcolm. Outside of an elaborate solution, this one may not be possible. As soon as the session expires, Django updates the records in the django.sessions table. As such, the only unique identifier for the user, "session_key", is overwritten. If there is some straightforward way to intercept the call to update that table at the time of the automated logout, I'm all ears. On Mar 17, 9:28 pm, Paulo Köch <paulo.k...@gmail.com> wrote: > > Calling logout(), as the original poster requested doesn't achieve > > anything (it does nothing). If it did do something, it would still be a > > bad idea to call it, because the user could have already logged in again > > and logging them out would be unfortunate. > > Doesn't this generate a new session_id? > > Cheers, > Paulo Köch --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
