On 19 ?.?. 2010, at 22:25, Tom Evans wrote: >>>> The server is running Apache 2.2.12 on Ubuntu. >>> >>> You are running in a threaded environment then, your sessions can't persist >>> without cookies or equivalent external storage because the HTTP exchange is >>> not all contained within the same server process... >> >> Whoops, I couldn't cancel that e-mail fast enough, but I'm clearly wrong - >> cause you mentioned that it's only a problem in IE, but that it's working in >> Chrome and Firefox. So maybe you're not using a threaded Apache. Sorry for >> jumping to conclusions! >> >> Jonathan >> > > What has that got to do with the price of cheese?
You're absolutely right, it's got nothing to do with it at all, HTTP is stateless, even if I were reaching, thinking of persistent TCP connections, they're on the layer below so it couldn't matter. Sorry about that, it's 11:30pm my time and I didn't get to sleep last night, so I have to beg your forgiveness for having spread nonsense. > All web servers are > stateless, threaded or otherwise. Yeah, of course, I was confusing myself with a problem I just encountered trying to persist non-serializable objects (socket connections) that I couldn't find a work around for under MPM Apache. Ended up with an ugly kludge involving a hidden iframe - almost as shameful as the incorrect responses I offered in this thread... > Sessions are a layer added above > HTTP by your framework. To be frank, none of your replies have made > sense to me - It's good you're frank, I won't feel my mistake is perpetuating itself into impressionable minds. I hope I've helped people with their problems slightly more often than I've mis-lead them in my short time on this list to date, but perhaps I've been too eager to spread my newbie enthusiasm. On the other hand, I'm personally very grateful for the consistently high-quality information and advice you share on this list, I've learned quite a lot about Django from reading your posts every day. Thanks! > django does not use client side sessions, and doesn't > hash the data in a session.. I didn't mean to say that it included any session data in the cookie, just that it hashed the session ID that's stored there, per http://www.djangobook.com/en/2.0/chapter14 : "Cookies use only a hashed session ID -- not the data itself -- thus protecting you from most of the common cookie problems." But I mis-spoke... Anyway, you've set Ben down the right path to understanding, so I'll just go finish debugging so I can finally get some sleep... Yours apologetically, Jonathan -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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.
