#23887: Invalid multipart boundary causes internal server error
-------------------------------------+-------------------------------------
Reporter: timgraham | Owner: claudep
Type: Bug | Status: assigned
Component: HTTP handling | Version: 1.7
Severity: Normal | Resolution:
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 aaugustin):
* stage: Accepted => Ready for checkin
Comment:
Right, it looks like it isn't the best choice in that case. I just wanted
to make sure it had been considered :-)
I left a small suggestion on the PR, otherwise this is good to go.
--
Ticket URL: <https://code.djangoproject.com/ticket/23887#comment:5>
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.7bbb76d876183580857b206c6ca43d96%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
