#30565: Close StreamingHttpResponse content immediately after iterating it
-------------------------------------+-------------------------------------
Reporter: Chris Jerdonek | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: HTTP handling | Version: master
Severity: Normal | Resolution:
Keywords: HttpResponse, | Triage Stage:
streaming, StreamingHttpResponse | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Carlton Gibson):
Hmmm.
There's a comment by `HttpResponseBase.close()`:
{{{
# The WSGI server must call this method upon completion of the
request.
# See http://blog.dscpl.com.au/2012/10/obligations-for-calling-close-
on.html
}}}
We're saying that's not the case?
I'm thinking this probably needs to go via the DevelopersMailingList to
get more input.
--
Ticket URL: <https://code.djangoproject.com/ticket/30565#comment:2>
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.9b6cdb5ce6cdf4fc41a1ef56a63cd732%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
