#17834: ETag generated from empty content can break http caching
-------------------------------------+-------------------------------------
Reporter: paulegan | Owner: nobody
Type: Bug | Status: reopened
Component: HTTP handling | Version: 1.3
Severity: Normal | Resolution:
Keywords: | Triage Stage: Design
Has patch: 1 | decision needed
Needs tests: 1 | Needs documentation: 0
Easy pickings: 0 | Patch needs improvement: 0
| UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by rene.puls@…):
* cc: rene.puls@… (added)
Comment:
I just stumbled over the same problem and would like to add another
possible solution.
The RFC says this about redirect responses (e.g. section 10.3.2): "Unless
the request method was HEAD, the entity of the response SHOULD contain a
short hypertext note with a hyperlink to the new URI(s)." While this is
not a requirement, it would help in this scenario, because the response
body (and thus the ETag) would then depend on the redirect URL.
--
Ticket URL: <https://code.djangoproject.com/ticket/17834#comment:9>
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 [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
