#15785: HttpRequest.read(NUM_BYTES) can read beyond the end of wsgi.input
stream.
(Violation of WSGI spec & under-defined behaviour)
---------------------------------------+-----------------------------
Reporter: tomchristie | Owner: tomchristie
Type: Bug | Status: new
Milestone: 1.3 | Component: HTTP handling
Version: 1.3-rc1 | Severity: Normal
Resolution: | Keywords: http, wsgi
Triage Stage: Accepted | Has patch: 1
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 |
---------------------------------------+-----------------------------
Comment (by tomchristie):
Added some extra tests and cleaned up some test code to also include the
test for #14753, which has similar logic.
I've added this as '''limited_stream_lazy_plus_extra_tests.2.diff'''.
As a final sanity check I reverted, applied the tests patches only, these
two fail:
* test_read_numbytes_from_empty_request
* test_read_numbytes_from_nonempty_request
applied the code patches, checked they passed.
Ivan, could you review, I'm guessing this should be able to go into 'Ready
for checkin' now.
Ta! :)
--
Ticket URL: <http://code.djangoproject.com/ticket/15785#comment:6>
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.
