#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
--------------------------------------+------------------------------------
Comment (by timgraham):
Some data about the rest of the behavior of `conditional_content_removal`
(discarding the content of responses with 1xx, 204, and 304 status codes):
Python's `BaseHTTPRequestHandler` (which `runserver` uses) also has
[https://github.com/python/cpython/blob/d616dc4ea9d63d9a9b52a95b887b9a49859092e8/Lib/http/server.py#L462-L466
discards the response content] for 204 and 304 status codes. I observed
the same behavior from gunicorn as well.
I also don't get any response data on HTTP 1xx responses regardless of
whether or not `conditional_content_removal` is active.
--
Ticket URL: <https://code.djangoproject.com/ticket/26052#comment:7>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.47d500ea6379b4f382038373dd72afd9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
