Opened 7 years ago

Closed 7 years ago

#28093 closed Bug (invalid)

Parsing of multipart/form-data broken since 1.10.x series

Reported by: Ricardo Kirkner Owned by: nobody
Component: HTTP handling Version: 1.11
Severity: Normal Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


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/ 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.

Change History (1)

comment:1 by Ricardo Kirkner, 7 years ago

Resolution: invalid
Status: newclosed

Sorry for the noise. This was really an issue with django-piston getting in the way and overwriting the content_type after Django already parsed it.

Note: See TracTickets for help on using tickets.
Back to Top