#16461: Saving the user's preferred language in the session causes browser
caching
problems
-------------------------+--------------------------------------
Reporter: cnorthwood | Owner: nobody
Type: New feature | Status: new
Milestone: | Component: Internationalization
Version: 1.3 | Severity: Normal
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------+--------------------------------------
If the user's preferred language is saved in the session, rather than as a
cookie, and if you are using page caching with Expires: headers, any pages
which the user loaded before switching languages will be loaded from the
browser cache, in the old language, as opposed to the newly switched to
language!
If it was saved in the cookie, the Vary: Cookie header will cause the
browser cache to be invalidated when the language (hence cookie) changes,
but if the SessionMiddleware is being used, then it is used there. What
would be nice is an option to force the locale middleware (and
set_language view) to always use cookies, even if the session middleware
is loaded. Perhaps even getting rid of the session storage completely -
using cookies will stop gotchas like this imo!
--
Ticket URL: <https://code.djangoproject.com/ticket/16461>
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 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.
