I'm running a site with 2 front end servers (lighttpd with django in fcgi daemons) and one database server (MySQL). The two front end servers are in DNS round-robin so a user might get some content from one and some from the other in any given session. All this works fine and has had no problems for the past year it's been live.
Now we're starting to actually use the Django authentication middleware and admin interface on the production servers and it's logging out users whenever their browser makes multiple requests or bounces between servers. What's going wrong? Does Django not store sessions in the database? Is the auth framework caching instead of going back to the database server? Thanks for your help, Matthew -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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.
