#8616: File-based sessions dropped with SESSION_SAVE_EVERY_REQUEST = True
----------------------------------------------+-----------------------------
Reporter: [EMAIL PROTECTED] | Owner: nobody
Status: new | Milestone: 1.0
Component: django.contrib.sessions | Version: SVN
Resolution: | Keywords: session, file,
race
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
----------------------------------------------+-----------------------------
Changes (by [EMAIL PROTECTED]):
* summary: Session file corrupted with SESSION_SAVE_EVERY_REQUEST = True
=> File-based sessions dropped with
SESSION_SAVE_EVERY_REQUEST = True
Comment:
On further research it appears that the session file is not corrupted, but
just appears to be corrupted because it is read at the same time another
request is writing it. Because the failed attempt by the second request
to decode the session data results in the generation of a new session key,
the (now empty) session data is written to a new file, not the old one.
Requests that use the original session id get the original session data
intact, so long as another request is not in the process of writing it.
--
Ticket URL: <http://code.djangoproject.com/ticket/8616#comment:5>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
