#23887: Invalid multipart boundary causes internal server error
-----------------------------------------+------------------------
Reporter: timgraham | Owner: nobody
Type: Bug | Status: new
Component: HTTP handling | Version: 1.7
Severity: Normal | Keywords:
Triage Stage: Accepted | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-----------------------------------------+------------------------
Reported by Antti Häyrynen and verified by me.
In http/request.py `_load_post_and_files` when calling
`self.parse_file_upload` failures raise `MultiPartParserError`, which
causes http request handler to throw 500 in case multipart has something
wrong (invalid boundary and apparently negative content length). I think
bad request would be better response to this.
Attached is a sample HTTP request, which has a bell in mime boundary that
makes django return 500.
To reproduce (you must have the admin installed so /admin/login/ doesn't
404):
{{{
$ nc 127.0.0.1 8000 < beep-500.httpreq
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/23887>
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/052.f44899be12a4f8bd76488c8771d1b2c9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
