Hi Matt, All that the SESSION_COOKIE_AGE changes is the expire_date on a "session" entry in one of your database tables. If you change SESSION_COOKIE_AGE, but are still logged in, then that date is still going to be about two weeks in the future. Try logging out, and setting the COOKIE_AGE to something more realistic (like 60, for testing purposes).
As for SESSION_COOKIE_AGE = 0, if I remember correctly this just means the expire_date is the maximum date the database can support. This means the cookie will not be removed until the user manually logs out. On the project website you will see that this was an intentional design, although there is little discussion as to the pros and cons of using this vs. the more typical behaviour (that you are describing). You can set SESSION_SAVE_EVERY_REQUEST to True which might provide what you want. Really its all here tho :) http://www.djangoproject.com/documentation/sessions/ -rob --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
