#17305: Cache middleware keys too difficult to customize
-------------------------------------+-------------------------------------
Reporter: subsume | Owner: subsume
Type: | Status: new
Cleanup/optimization | Version:
Component: Core (Cache system) | Resolution:
Severity: Normal | Triage Stage:
Keywords: | Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by subsume):
Also I think there's an oversight in the Fetch middleware:
https://code.djangoproject.com/browser/django/trunk/django/middleware/cache.py#L133
Perhaps someone can inform me if I am being ignorant, but the Fetch
middleware seems to make no reference to
settings.CACHE_MIDDLEWARE_UNAUTHENTICATED_ONLY before creating a
connection to cache and checking for the value. The only reason it happens
to work in the current setup is because the Update happens to skip
creation of a key. So even though I have explicitly set UNUAUTH=True, when
I use a key that isn't generated by the above utils, it will result in my
auth users getting a cached version.
Began ticket about this #17313
--
Ticket URL: <https://code.djangoproject.com/ticket/17305#comment:3>
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.
