#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 carljm):
That proposal sounds right to me; I don't have a better plan. Presumably
there would be two deprecation warnings, one for
`SessionAuthenticationMiddleware` (which would be a no-op, other than
being checked for as an alternative to `settings.AUTH_VERIFY_SESSION`),
and one for `settings.AUTH_VERIFY_SESSION = False`.
Do we have precedent for adding deprecations in a minor version? Maybe the
deprecation warnings should be added only in master, and not in the
backport? I guess adding the warnings in the backport gets people aware of
the issue earlier, but it seems slightly backwards-incompatible to add
deprecation warnings in the middle of a release series.
--
Ticket URL: <https://code.djangoproject.com/ticket/23939#comment:9>
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.3868599af5fad141fa1407e20bdbcff1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
