#17313: Cache FetchMiddleware checks cache for auth despite UNAUTH_ONLY=True
-------------------------------------+-------------------------------------
Reporter: subsume | Owner: nobody
Type: Bug | Status: closed
Component: Core (Cache system) | Version:
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage:
Has patch: 0 | Unreviewed
Needs tests: 0 | Needs documentation: 0
Easy pickings: 0 | Patch needs improvement: 0
| UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by ptone):
* status: new => closed
* resolution: => invalid
Comment:
I believe the setting you are referring to is:
CACHE_MIDDLEWARE_ANONYMOUS_ONLY
If a the content and associated key does not involve any user specific
data, then it can be cached as if that user were an anonymous user. The
logic for this is actually in
{{{UpdateCacheMiddleware._should_update_cache}}}
see discussion and fix associated with: #13283
also note: #15201
--
Ticket URL: <https://code.djangoproject.com/ticket/17313#comment:2>
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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
