#23887: Invalid multipart boundary causes internal server error
-------------------------------------+-------------------------------------
Reporter: timgraham | Owner: claudep
Type: Bug | Status: closed
Component: HTTP handling | Version: 1.7
Severity: Normal | Resolution: fixed
Keywords: | 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 Claude Paroz <claude@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"b38637d5813f014fbe3e031253a166c208c387e1"]:
{{{
#!CommitTicketReference repository=""
revision="b38637d5813f014fbe3e031253a166c208c387e1"
Fixed #23887 -- Returned Bad Request for multipart parsing fails
Thanks Antti Häyrynen and Tim Graham for the report, and Aymeric
Augustin for the review.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/23887#comment:6>
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.c0d19b3c76ce2df29b292a135526817c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
