#25489: SESSION_SAVE_EVERY_REQUEST Appears to have broke in 1.8.4
----------------------------------+--------------------------------------
Reporter: thornomad | Owner: nobody
Type: Uncategorized | Status: new
Component: contrib.sessions | Version: 1.8
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+--------------------------------------
Comment (by thornomad):
Well ... I am certainly no expert on security and would defer to a wiser
cohort! Smile.
From my standpoint, it seems like the expected behavior of
`SESSION_SAVE_EVERY_REQUEST` has changed. The outcome it was producing
was what I had come to expect. By adding the `and not Empty` in that
patch doesn't it kind of negate the setting itself (because I thought the
setting was supposed to force it to save even if it was empty) ... or am I
misunderstanding that?
--
Ticket URL: <https://code.djangoproject.com/ticket/25489#comment:2>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.5315ceca772605ec7a89750f9e1b304a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
