title: Issues with valid multipart/mixed and Google Drive
body: <p>I am attempting to upload a file to Google Drive using the "upload" URL with a type of "multipart". I'm trying to do this without a library and using basic HTTP with a multipart POST. With a body like the following, I am constantly getting the error "Invalid multipart request with 0 mime parts."</p>
  
  <ol>
  <li>The HTTP message looks valid to me. Is there something obvious that I'm missing or doing wrong?</li>
  <li>Is there a protocol tester that can verify if my POST body is valid or not?</li>
  </ol>
  
  <p><code><pre>
  POST /upload/drive/v2/files?uploadType=multipart HTTP/1.1
  Authentiction: Bearer {valid auth_token}
  Content-Type: multipart/mixed; boundary="--314159265358979323846"
  host: localhost:3004
  content-length: 254
  Connection: keep-alive</p>
  
  <p>--314159265358979323846
  Content-Type: application/json</p>
  
  <p>{"title":"Now","mimeType":"text/plain"}
  --314159265358979323846
  Content-Type: text/plain
  Content-Transfer-Encoding: 8bit</p>
  
  <p>Mon Jun 17 2013 20:59:02 GMT-0400 (EDT)
  --314159265358979323846--</p>
  
  <p></pre></code></p>
  
  <p>(The segments look like they have double newlines. I think this is an artifact of the pasting, they are CRLF pairs in the code and appear as a newline when testing, but I guess this could theoretically be the problem, but I'd like proof.)</p>