I tried it on my notebook with the django server, the cookie wasn't touched, but request.session.session_key changes every request.
Using the db session backend avoid login, cached_db and cache works temporally. In summary: * On the server (etch) session flushes by request.user.is_authenticated() (e.g session.user switched to anonymous without any findable reason) after a while equal if session still marked active in database and cookie. * On Ubuntu exactly the same application changing the key every request but session in cookie is still the first key. * There is no difference if I use Django-server instead of Apache. * I have no idea how I can test such things in python-shell, because I found no way to create a working request object or save one to a file. The Django modules feeling like a Blackbox, docs only shows a minimum overview how it should work. * Django is even more frustrating for me than the PHP-crap, and that is extreme frustrating (I love Python and it never frustrates me like this). grrreets, florian --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
