Dear All Is the setting SESSION_EXPIRE_AT_BROWSER_CLOSE mis-named? As far as I can tell the setting doesn't influence the session expiry at all (e.g., what happens to the django_session table on the server). What this setting seems to affect is the expiry of the *cookie* in the browser.
I'm looking into a way for django to detect users no longer on the site (i.e. authenticated users who rather than logout, have navigated away from the site or closed their browser). From the name, I had thought this setting would be useful. It looks like it'll be useful for the client side, but for the server side it's irrelevant surely? A clearer name would be something like SESSION_COOKIE_EXPIRE_AT_BROWSER_CLOSE. Best wishes Ivan -- 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.
