#15668: Generic views should provide a HEAD implementation
-----------------------------------------+----------------------
Reporter: j4mie | Owner: nobody
Status: new | Milestone:
Component: Generic views | Version: 1.3
Resolution: | Keywords:
Triage Stage: Unreviewed | Has patch: 1
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 1 |
-----------------------------------------+----------------------
Comment (by grahamd):
Python web applications should never themselves discard the response
content for HEAD requests. They should always return the request content
and allow the underlying WSGI server or hosting web server to discard the
request content. If you don't do that and discard request content anyway,
you violate the principal that GET and HEAD should return the same
headers, because by removing the response content you prevent a WSGI
middleware or web server output filter from processing response content
and modifying the response headers. Go read
'http://blog.dscpl.com.au/2009/10/wsgi-issues-with-http-head-
requests.html'.
So, if Django is already itself dropping response content for HEAD
requests, it technically is not a well behaved WSGI application.
--
Ticket URL: <http://code.djangoproject.com/ticket/15668#comment:5>
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 [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.
