#28093: Parsing of multipart/form-data broken since 1.10.x series
-------------------------------------------+------------------------
Reporter: Ricardo Kirkner | Owner: nobody
Type: Bug | Status: new
Component: HTTP handling | Version: 1.11
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------------+------------------------
It looks like recently (since commit
6f1318734f0f3b6e62b782b0251a4e676e542e0b) the parsing of the multipart
/form-data content has broken.
The test client is submitting data encoded as multipart/form-data;
boundary=BoUnDaRyStRiNg but in django/http/request.py multipart/form-data
content is only properly parsed when the content type matches exactly
'multipart/form-data'. In all other cases the request.POST data is left
empty.
--
Ticket URL: <https://code.djangoproject.com/ticket/28093>
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/057.cfaa4137d6b804288b9f1752a4268435%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
