Cookie=sessionid=6bc37c43a444db3aaf60a5c61e85bb01; support_tabs=0
Content-Type=application/x-www-form-urlencoded
Content-Length=52
POSTDATA=username=moneybags&password=dollars&next=%2F&x=0&y=0
this is the relevant tamperdata output, though i'm not necessarily
sure how to check if the session cookie is being set (i don't know
what it should look like), but it's definitely routing to the correct
path ('/'). And i've only had this issue with django 1.0, i'd ported
this project over from a DEV box running .96 and everything worked
great; now the login function seems to hate me. Any ideas?
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
