title: bad content-type header, no multipart boundary nodejs
body: <p>I have an API that returns content with <code>content-type: "multipart/form-data; charset=utf-8"</code>. However, in my nodejs app, when I make the following call through <code>superagent</code>:</p>
  
  <pre><code>request
      .get(ApiUrl + id)
      .set('Authorization', basicHttpAuth)
      .set('client_id', clientId)
      .set('client_secret', clientSecret)
      .end(function (err, res) {
          if (err) {
              callback(null, err)
              console.log(err);
          }
          else {
              callback(null, res);
          }
      })
  </code></pre>
  
  <p>I get this error:</p>
  
  <blockquote>
    <p>Error: bad content-type header, no multipart boundary</p>
  </blockquote>
  
  <p>Any idea what's wrong?</p>
  
  <p>Stack Trace:</p>
  
  <pre><code>Error: bad content-type header, no multipart boundary
      at IncomingForm._parseContentType (/Users/mike/Svr/Server/node_modules/formidable/lib/incoming_form.js:271:19)
      at IncomingForm.writeHeaders (/Users/mike/Svr/Server/node_modules/formidable/lib/incoming_form.js:142:8)
      at IncomingForm.parse (/Users/mike/Svr/Server/node_modules/formidable/lib/incoming_form.js:110:8)
      at ClientRequest.&lt;anonymous&gt; (/Users/mike/Svr/Server/node_modules/superagent/lib/node/index.js:869:9)
      at Object.onceWrapper (events.js:316:30)
      at emitOne (events.js:115:13)
      at ClientRequest.emit (events.js:210:7)
      at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:564:21)
      at HTTPParser.parserOnHeadersComplete (_http_common.js:116:23)
      at TLSSocket.socketOnData (_http_client.js:453:20) response: undefined }
  </code></pre>
  
  <p>Here is the server response header:</p>
  
  <pre><code>Access-Control-Allow-Origin →*
  Connection →keep-alive
  Content-Length →44691
  Content-Type →multipart/form-data; charset=utf-8
  Date →Wed, 05 Jul 2017 03:44:23 GMT
  </code></pre>
  
  <p>And the body is big blob of text / string.</p>