On Thu, 2006-06-08 at 02:21 +0300, Elver Loho wrote: > On 6/8/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote: > > > > On 6/7/06, Elver Loho <[EMAIL PROTECTED]> wrote: > > > This behaviour is just way too weird. I'm currently developing with > > > Django for work and with CherryPy for a side project and CherryPy > > > doesn't store sessions beyond the lifetime of the server. I sort of > > > didn't expect this behaviour from Django either. > > > > > > So, this a bug or a feature? And how can I turn it off? > > > > Turn it off with the SESSION_EXPIRE_AT_BROWSER_CLOSE setting. > > That simply sets the cookie to expire when the browser is closed. > That's not a solution since I've got Firefox open in 3-4 workspaces > here, with several tabs in each instance. I'm sure as hell *not* going > to close every last instance every time I change something in the code > and want to start all over again... > > I think it's a bug that Django's session variables survive when the > Django development server is closed. Yes, when I close the browser, > it's nice that I can start it again and be greeted with my session. > However, when I close the server, I expect the session to be lost.
Move beyond the development server for a moment and think about sessions in the more general concept. Generally, it is not desirable for a client's session to be lost just because the backend webserver is restarted. Session-based cookies behave according to browser lifetime, not server lifetime. However, if you want the server to no longer recognise the client's cookie, then the solution is to clear out the django_session table from the database each time. I'm not sure this is really something we want to do each time we stop and start -- because most of the time you don't want to have to re-login and everything. But if you do need it all the time, then it is easy enough to create a shell script that runs "delete from django_session" prior to doing "exec manage.py runserver". Or catch the termination the dev server and do the deletion at that point, although that is a little more fiddly. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
