Setting SESSION_ENGINE to 'django.contrib.sessions.backends.cached_db' in Django 1.1 solved my problem. Sorry for my "spam".
On Aug 19, 2:03 pm, Kelvan <kelvan.mailingl...@gmail.com> wrote: > Tested without apache on the server, seems to work. > I think my problem has another reason. > > On Aug 19, 1:05 pm, Kelvan <kelvan.mailingl...@gmail.com> wrote: > > > I have a similar problem with FF and Etch (with Django 1.0 and 1.1 > > tested). > > Works when running on my notebook (Ubuntu 9.10a4 with Django 1.1). > > I'm using Apache/mod_python. > > > On 13 Aug., 23:07, humble <eyuw...@gmail.com> wrote: > > > > Hi Malcolm > > > > Thanks for your suggestion. I did to try using a FQDN to configure IE > > > for cookies. I am still seeing requests coming in from IE do not carry > > > a cookie...... > > > > What am I doing wrong? > > > > On Aug 12, 9:48 pm, Malcolm Tredinnick <malc...@pointy-stick.com> > > > wrote: > > > > > On Wed, 2009-08-12 at 19:21 -0700, humble wrote: > > > > > Hi, > > > > > > I am writing a web application that involves session management with > > > > > the corporate backend module. I wrote my own authentication backend > > > > > plugin to satisfy the corporate requirement, not the default > > > > > authentication backend. I use file based session engine to avoid > > > > > sqlite crap. Everything works fine in firefox and chrome. But it seems > > > > > to be a problem with IE: response includes a new session ID (actually > > > > > a test cookie) for each request from IE. It seems IE never sends back > > > > > the previous cookie given by the server in subsequent request. Check > > > > > in /tmp/ (where I store all session files), I see the previous session > > > > > file is replaced with a new empty session file. > > > > > > Looking in to contrib.session.middleware.py confirms > > > > > "request.session.session_key" is different for each request. However, > > > > > this only happens when I use IE. I configured IE 7 to allow cookies, > > > > > so it does not reject cookies from django. What might be the problem? > > > > > Has any one seen this issue before? > > > > > I've seen it before when the domain being used for the cookie wasn't a > > > > valid domain name. Browsers have blacklists of sets of domains that they > > > > won't accept/send cookies for and they typically won't allow you to set > > > > a cookie for .com, say. > > > > > That might be the problem in this case. > > > > > 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
