#13283: CACHE_MIDDLEWARE_ANONYMOUS_ONLY kills anonymous caching efficiency
-----------------------------------+----------------------------------------
Reporter: carljm | Owner: nobody
Status: new | Milestone:
Component: Cache system | Version: SVN
Resolution: | Keywords: session accessed vary
cookie
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 1 |
-----------------------------------+----------------------------------------
Comment (by silviogutierrez):
As far as I can tell (not scientifically tested), if you place
django.middleware.cache.UpdateCacheMiddleware *under* the session
middleware (doing what the documentation tells you *not* to do), then the
cache middleware will behave correctly in the basic form. That is,
anonymous users see a cached page, and logged in users don't. If you turn
off CACHE_MIDDLEWARE_ANONYMOUS_ONLY, then both types of users see a cached
page.
However, this solution probably breaks some more refined controls using
Vary. As I don't use these though, this is a good temporary solution till
the problem is fixed.
--
Ticket URL: <http://code.djangoproject.com/ticket/13283#comment:11>
Django <http://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.
