2010/10/19 Jonathan Barratt <jonathan.barr...@knifeict.com>: > > On 19 ต.ค. 2010, at 21:49, Jonathan Barratt wrote: > >> >> On 19 ต.ค. 2010, at 21:32, Quiet Light Development wrote: >> >>> Thank you Masklinn and Jonathan for your responses. I don't know a lot >>> about the physical set-up of the system, I can ask the server >>> administrators that question. >>> >>> 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? All web servers are stateless, threaded or otherwise. Sessions are a layer added above HTTP by your framework. To be frank, none of your replies have made sense to me - django does not use client side sessions, and doesn't hash the data in a session.. Django's framework uses cookies (and only cookies) to persist the session identifier in a users browser. The session identifier is retrieved from the session id cookie on subsequent requests and used by the session backend to load the session data for that user. Have you enabled the session middleware? Do you have 'django.contrib.sessions.middleware.SessionMiddleware' in MIDDLEWARE_CLASSES? Is the django session cookie being set? Since your issue seems to be with Internet Explorer, you should install fiddler2 to examine the request/responses being sent/received by your browser. Check that django is setting a session cookie (the response will have a header called Set-Cookie), and that your browser is accepting the cookie and returning it with the next request (the request will have a header called Cookie). A common problem when browsers not not accepting cookies is that the cookie is emitted with an invalid domain. The browser receives the cookie, but seeing the domain is invalid, refuses to store it. Cheers Tom -- 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.
