#23939: SessionAuthenticationMiddleware causes "Vary: Cookie" header no matter
what
---------------------------------+-------------------------------------
Reporter: andrewbadr | Owner: timgraham
Type: Bug | Status: assigned
Component: contrib.auth | Version: 1.7
Severity: Release blocker | Resolution:
Keywords: cookies | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+-------------------------------------
Comment (by timgraham):
I don't know of a use case to disable the behavior in the long-term.
For backwards compatibility, we could guard the new verification logic in
`auth.get_user()` with `if
'django.contrib.auth.middleware.SessionAuthenticationMiddleware' in
settings.MIDDLEWARE_CLASSES` or `settings.AUTH_VERIFY_SESSION`. The new
`settings.AUTH_VERIFY_SESSION` defaults to `False` and goes through the
normal deprecation cycle (set it to `True` to disable the warning). As
sessions naturally expire and are recreated, they are "upgraded" to
include the verification hash, so presumably you could flip the setting
after some time of running 1.7 in production and lose a minimal amount of
sessions, if any.
--
Ticket URL: <https://code.djangoproject.com/ticket/23939#comment:8>
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/068.350cbdd3a8b22b145a3a7670a9aae9f0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
