#13222: unexpected HttpResponse iteration behavior
-------------------------------------+-------------------------------------
Reporter: teepark | Owner: nobody
Type: Bug | Status: reopened
Milestone: | Component: HTTP handling
Version: 1.3-rc1 | Severity: Normal
Resolution: | Keywords:
Triage Stage: Design | Has patch: 1
decision needed | Needs tests: 0
Needs documentation: 0 |
Patch needs improvement: 0 |
-------------------------------------+-------------------------------------
Comment (by grahamd):
In some respect this is an issue which could perhaps be brought up on
Python WEB-SIG because what you are talking about is how the iterable
returned by a WSGI application should behave. I know for anything I have
seen and implemented, use of an iterator causes data to be consumed and
it wouldn't be rewound to the original beginning of the data if a new
iterator were created as Django seems to be doing by what is described
here. So, perhaps another odd corner case for WSGI specification which
should be clarified.
--
Ticket URL: <http://code.djangoproject.com/ticket/13222#comment:14>
Django <http://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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
