#16201: When Content-Length is 0, MultiPartParser violates RFC2616
-------------------------------------+-------------------------------------
Reporter: albsen | Owner: nobody
Type: Bug | Status: closed
Milestone: | Component: HTTP handling
Version: 1.3-rc1 | Severity: Normal
Resolution: fixed | Keywords: http multipart
Triage Stage: Ready for | Has patch: 1
checkin | Needs tests: 0
Needs documentation: 0 | Easy pickings: 0
Patch needs improvement: 0 |
UI/UX: 0 |
-------------------------------------+-------------------------------------
Changes (by russellm):
* status: new => closed
* resolution: => fixed
Comment:
In [16353]:
{{{
#!CommitTicketReference repository="" revision="16353"
Fixed #16201 -- Ensure that requests with Content-Length=0 don't break the
multipart parser. Thanks to albsen for the report and patch
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/16201#comment:3>
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 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.
