http api not validating if content-type header is present.

[wraithgar]

The 'add files' endpoint of the http api passes the content-type header down into ipfs-multipart, which passes it down into the content library which was not checking for that header's presence before trying to parse it, resulting in a traceback and 500 error.

This has been patched in content and a pr for ipfs-multipart has been opened here: ipfs-inactive/js-ipfs-multipart#1

When that PR is either merged or the issue addressed manually we can then update the ipfs-multipart dependency in this repo and close this issue.

[alanshaw]

Closing as ipfs-inactive/js-ipfs-multipart#1 has been merged