#26052: Consider removing conditional_content_removal
------------------------------------------------+------------------------
Reporter: aaugustin | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: HTTP handling | Version: 1.9
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
------------------------------------------------+------------------------
It's the last survivor of the "response_fixes" and I think it should go
away.
Graham Dumpleton has described better than I would why frameworks should
leave the task stripping the body of HEAD requests to servers:
http://blog.dscpl.com.au/2009/10/wsgi-issues-with-http-head-requests.html
(first five paragraphs).
We should check whether mod_wsgi, gunicorn and uwsgi properly strip the
body of HEAD requests before proceeding. We should also move that behavior
into runserver -- that is, on the other side of the WSGI.
--
Ticket URL: <https://code.djangoproject.com/ticket/26052>
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/052.7cf34ed47fffc1c58bb87e0038cb8434%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
