Look at the thing I posted. The sessionid= tag is there but it seems to confuse django when there's more than just that in that header. I don't know exactly what causes it though.
On May 7, 4:28 pm, finnam <[EMAIL PROTECTED]> wrote: > Isn't it just a matter of session id cookie name? You should have > different session id cookies for java app server and django. > > On May 7, 12:23 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > > > Ahh, I figured it out. There was a java app server running on this > > machine before and I for some reason that caused django to choke. I > > removed all of them and now it works. > > > Does this seem like a bug? --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
