#26052: Consider removing conditional_content_removal
--------------------------------------+------------------------------------
Reporter: aaugustin | Owner: susan
Type: Cleanup/optimization | Status: assigned
Component: HTTP handling | Version: 1.9
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Old description:
> 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.
New description:
It's the last survivor of the "response_fixes" and I think it should go
away. Its origin is #5898.
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.
--
Comment (by timgraham):
I observed that gunicorn and runserver (based on Python's server) don't
send content for HEAD requests. I didn't check mod_wsgi or uwsgi since
they are marginally more complicated to setup a test project. If we go
ahead and remove this, one place where developers might see a difference
would be in the test client. Do you think it's worth trying to keep it in
that context? I lean toward simply removing it and reacting if anyone
complains.
--
Ticket URL: <https://code.djangoproject.com/ticket/26052#comment:6>
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/067.704a6f83ffa529a89abe9c1c0416254b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
