Django session key collision

[Greg]

I've noticed a number of apparent session collisions (i.e., two or more users getting the same session key and therefore each others session data) on a site I manage. The site is on django 1.3.7, which shouldn't have any issues with session key collisions (there were some in earlier django versions) but I don't know whether it's entirely thread safe?

How would I go about debugging this? I can't reproduce the bug so at a bit of a loss as to how to fix it.

[Avraham Serour]

can you reproduce the bug? can you use a more recent django version?

On Wed, Jun 3, 2015 at 6:10 AM, Greg <gregpla...@gmail.com> wrote:

I've noticed a number of apparent session collisions (i.e., two or more users getting the same session key and therefore each others session data) on a site I manage. The site is on django 1.3.7, which shouldn't have any issues with session key collisions (there were some in earlier django versions) but I don't know whether it's entirely thread safe?

How would I go about debugging this? I can't reproduce the bug so at a bit of a loss as to how to fix it.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users...@googlegroups.com.
To post to this group, send email to django...@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/8b1e5d0d-8fe9-4a6d-87a6-2ee275c840ef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.