On Thu, Oct 9, 2008 at 3:25 PM, Robocop <[EMAIL PROTECTED]> wrote: > > All right, this is getting absolutely ridiculous. I tried to > workaround my problems by using the built in contrib.auth.views.login, > and of course this resulted in the same behavior. I am very reluctant > to think this is a bug, but rather some type of session > misunderstanding, but i'm running out of options. I'm getting > desperate on this project and would really really appreciate some type > of constructive commentary, no matter how outrageous. > >
One thing you can do (below the django level) is to use TamperData for firefox or something similar to examine your headers and make sure the session cookie is indeed being set, with the right path. Always good to confirm that if you're having weird session behavior. Are you experiencing this on the development server, or some other setup? Colin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
