#25782: Discourage usage of cache_page decorator with UpdateCacheMiddleware (or make middleware ignore decorated views) -------------------------------+-------------------------------------- Reporter: int-ua | Owner: nobody Type: Uncategorized | Status: new Component: Documentation | Version: master Severity: Normal | Resolution: Keywords: | Triage Stage: Unreviewed Has patch: 0 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 -------------------------------+-------------------------------------- Changes (by carljm):
* needs_better_patch: => 0 * needs_tests: => 0 * needs_docs: => 0 Comment: Any attempt to fix this should also take into account #15855 -- the `cache_page` decorator is already basically broken in terms of Vary headers. It shouldn't cache at all, it should mark the response for later caching by the middleware, or something. -- Ticket URL: <https://code.djangoproject.com/ticket/25782#comment:1> 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 django-updates+unsubscr...@googlegroups.com. To post to this group, send email to django-updates@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/064.c29c48ac291c9fc45a3951470d8ca3ce%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.