#15855: cache_page decorator bypasses any Vary headers set in middleware
-------------------------------------+-------------------------------------
Reporter: carljm | Owner: nobody
Type: Bug | Status: new
Milestone: | Component: Core (Cache system)
Version: | Severity: Normal
Resolution: | Keywords:
Triage Stage: Design | Has patch: 1
decision needed | Needs tests: 0
Needs documentation: 0 | Easy pickings: 0
Patch needs improvement: 0 |
UI/UX: 0 |
-------------------------------------+-------------------------------------
Comment (by russellm):
There's two problems here:
1. The subject of this ticket -- that cache_page has problems because it
caches content too early in the process. This is the root problem.
2. The fact that the docs currently suggest that @vary_on_header and
@cache_page can be used on CSRF pages.
The second problem will be resolved when/if we fix the first problem, but
in the interim, the existence of the suggestion is pretty misleading.
Idan's patch looks good for that purpose.
--
Ticket URL: <https://code.djangoproject.com/ticket/15855#comment:4>
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.
