title: request.POST empty for Content-Type: multipart/form-data; boundary=xYzZY
body: <p><strong>[SOLVED] Please see my answer.</strong></p>
  
  <p>Any <code>POST</code> request sent with the 
  <code>Content-Type: multipart/form-data; boundary=xYzZY</code> results in the <code>request.POST</code> <code>QueryDict{}</code> to be empty. Changing the <code>Content-Type</code> to <code>multipart/form-data</code> also results in the same error.</p>
  
  <p>Removing the Content-Type altogether results in the values getting passed correctly, and I can access them in <code>request.POST</code>.</p>
  
  <p>I have tried disabling the Csrf middleware, using @csrf_exempt, and also tried the same on multiple servers. Didn't change the empty POST condition.</p>
  
  <p>While reading up on Django framework and POST content-type, I read that it (no longer) assumes a default content-type and therefore must be supplied with the correct one (I do not have a link to the article in question.) I think something similar is happening here, with django not being able to parse the parameters with the given content-type (but leaving it blank lets the parser interpret it with the default value). </p>
  
  <p>What I am having trouble with is, that the Content-Type value supplied is perfectly valid (multipart/form-data with boundary). So why does django refuse to load it in the POST dictionary?</p>
  
  <p>** I am not in control of the Content-Type sent in the POST data.</p>
  
  <p>** UPDATE: reading from <code>request.body</code> shows that all the <code>POST</code> parameters are being received. They're just not present in <code>request.POST</code></p>
  
  <p>** UPDATE: I'm using Runscope to test <code>POST</code> requests.</p>