#19052: HTTP POST Dictionary should not be populated unconditionally
-------------------------------+--------------------------------------
Reporter: eric@… | Owner: nobody
Type: Bug | Status: closed
Component: HTTP handling | Version: 1.4
Severity: Normal | Resolution: invalid
Keywords: http, post | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by claudep):
I think this is a valid concern and a duplicate of #5611. We currently
assume that POST content is either multipart or form-urlencoded. We are
not prepared to handle a POST request like:
{{{
POST /url HTTP/1.1
Host: www.example.com
User-Agent: ...
Content-Type: application/octet-stream
Content-Length: n
Here is binary content
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/19052#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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
