On Jan 5, 6:33 pm, Peter Rowell <[EMAIL PROTECTED]> wrote:
> > only save sessions which have been modified
>
> Actually, the code in the sessions/middleware is:
> if modified or settings.SESSION_SAVE_EVERY_REQUEST:
> so the whole point is to save it whether it's modified or not.
This wasn't related to your issue, just wanted to put out something
I'd been chewing on.
Specifically, there's no point in saving a session if it's empty and
hasn't been modified.
>
> But then you mentioned:
>
> > perhaps a misconfigured COOKIE_PATH
>
> Does "not configured" count as misconfigured? :-)
> Sheesh, do I ever feel stoopid.
No, I was just wondering whether you had set some weird setting -- the
defaults work fine for most.
> I just checked the site cookies with WebDeveloper Toolbar and the
> sessionid Host looks perfectly valid:
>
> So, that doesn't seem to be a problem ... is it?
>
> So, I'm back to ... what's with all of the rapid session creation?
Well if it's creating the cookie fine, then I'm not really sure!
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
