#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:  Accepted
    Has patch:  1              |      Needs documentation:  0
  Needs tests:  0              |  Patch needs improvement:  0
Easy pickings:  0              |                    UI/UX:  0
-------------------------------+------------------------------------

Comment (by aaugustin):

 Did you consider having `MultiPartParserError` inherit
 `SuspiciousOperation`?

 That would result in a 400 (if memory serves).

--
Ticket URL: <https://code.djangoproject.com/ticket/23887#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 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.4b77d0b36430050fe039dcae4c771742%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to