#28104: conditional view processing decorator adds stale ETag
------------------------------------+------------------------------------
Reporter: Syed Safi Ali Shah | Owner: nobody
Type: Bug | Status: new
Component: HTTP handling | Version: 1.11
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------------+------------------------------------
Comment (by Simon Charette):
The way conditional decorators are designed will make it hard to implement
1. which can already be worked around by explicitly setting
`response['Etag']` in the view once the ressources have been altered.
I think 2. is the way to go here with documentation mentioning
`response['Etag']` should be set manually when dealing with unsafe methods
(e.g. `PUT` conflict).
--
Ticket URL: <https://code.djangoproject.com/ticket/28104#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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/069.54565c405f97636c191e7ef8e5de1d73%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
