#27686: calls to request.user.is_authenticated returns vary by cookie header for
all users
-------------------------------------+-------------------------------------
Reporter: Jeff Willette | Owner: Jeff
| Willette
Type: Bug | Status: closed
Component: contrib.sessions | Version: 1.10
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage:
| Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Carl Meyer):
If you need a shared-cacheable response, then you simply need to avoid
ever checking the session at all: the response must be the same for ALL
users, regardless of their session or lack thereof. If you need a small
user-specific portion (e.g. a logged-in notice in the top right or
whatnot) in an otherwise shared-cacheable e.g. landing page, one technique
is to populate that user-specific portion with a separate Ajax request.
--
Ticket URL: <https://code.djangoproject.com/ticket/27686#comment:6>
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/069.60dcbff07ebd3d2f7c25bb972f93117c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.