#9163: CsrfMiddleware needs to reset ETag header
---------------------------------------------+------------------------------
Reporter: carljm | Owner: lukeplant
Status: new | Milestone:
Component: Contrib apps | Version: SVN
Resolution: | Keywords: csrf
Stage: Design decision needed | Has_patch: 1
Needs_docs: 0 | Needs_tests: 1
Needs_better_patch: 0 |
---------------------------------------------+------------------------------
Changes (by lukeplant):
* owner: nobody => lukeplant
Comment:
Hmm:
* Adding ETag specific code into core is bad
* Putting it into the !CsrfMiddleware doesn't make much sense either, but
since it created the mess, it ought to clean it up.
Personally, at the moment I'd go for the latter, and also for deprecating
the response post-processing part of !CsrfMiddleware in favour of the
template tag described in CsrfProtection.
--
Ticket URL: <http://code.djangoproject.com/ticket/9163#comment:7>
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 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
-~----------~----~----~----~------~----~------~--~---
