#7581: Middleware accessing HttpResponse.content breaks streaming HttpResponse
objects.
-------------------------------------+-------------------------------------
Reporter: mrmachine | Owner: ccahoon
Type: New feature | Status: closed
Component: Core (Other) | Version: master
Severity: Normal | Resolution: fixed
Keywords: stream HttpResponse | Triage Stage: Accepted
Content-Length | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by Aymeric Augustin <aymeric.augustin@…>):
In [changeset:"8b9b8d3bda09eb1b447631182d06c6c5e51425f6"]:
{{{
#!CommitTicketReference repository=""
revision="8b9b8d3bda09eb1b447631182d06c6c5e51425f6"
Removed compatibility code for streaming responses.
This code provided a deprecation path for old-style streaming responses.
Refs #6527, #7581.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/7581#comment:49>
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.6decb4546f7f9fc76e04270c3e774403%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
