This sounds a bit like the problem we had with sessions when we tried using
dynamodb for a session store. We reverted to using redis instead, so I
don't really know how to solve your problem, but I would take a look at the
session store. It could be as easy as some of the sessions were created
with django 1.8 and then being read by django 1.10 it isn't able to read
the information correctly (related to how the session object has been saved
on the server - I don't remember if the store is populated differently in
django 1.8 and django.10?)
2017-08-04 16:35 GMT+02:00 holger <mikael.holgers...@gmail.com>:
> After upgrading from Django 1.8 -> 1.10 I get alot of this exception:
> Internal Server Error: <<RANDOM_PAGE>>
> SuspiciousOperation at <<RANDOM_PAGE>>
> The request's session was deleted before the request completed. The user
> may have logged out in a concurrent request, for example.
> Unfortunately I am not able to reproduce it which makes it difficult for
> me to locate the error. The exceptions are triggered in the production
> Anyone had a similar issue and managed to figure out what it was?
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to email@example.com.
> Visit this group at https://groups.google.com/group/django-users.
> To view this discussion on the web visit https://groups.google.com/d/
> For more options, visit https://groups.google.com/d/optout.
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 post to this group, send email to firstname.lastname@example.org.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit
For more options, visit https://groups.google.com/d/optout.