Improving Uploads of Big Files via Web Browsers

This a a meta-issue tracking known issues and ongoing improvements related to uploads of big (1GB+) files in web browser contexts.

Invalid progress reporting:

[ ] Streaming versions of ipfs.files.add buffer entire data in memory before doing HTTP POST
- upstream: https://github.com/ipfs/js-ipfs-api/issues/842
[ ] Chromium crash when sending <200MB over js-ipfs-api
- IN PROGRESS waiting for release with upstream fix to stream-http: https://github.com/jhiesey/stream-http/pull/93
- related issues
- crash when dropping a big file (https://github.com/ipfs-shipyard/ipfs-companion/issues/464)
- Uploading big files crush page in Chrome (https://github.com/ipfs/js-ipfs-api/issues/654)
- upload-file-via-browser can only upload file size less than 165MB (https://github.com/ipfs/js-ipfs-api/issues/788)
[ ] Silent crash in Firefox when Buffer max size is breached:
- upstream issue: https://github.com/ipfs-shipyard/ipfs-companion/issues/464
- IN PROGRESS waiting for release with upstream fix to stream-http: https://github.com/jhiesey/stream-http/pull/93
[ ] Silent error while files.add over HTTP API (http: invalid Read on closed Body)
- go-ipfs: https://github.com/ipfs/go-ipfs/issues/5168 (should land in go-ipfs v0.4.19 - https://github.com/ipfs/go-ipfs/issues/5168#issuecomment-446804558)
  - IN PROGRESS https://github.com/ipfs/go-ipfs-cmds/pull/116
- js-ipfs-api: https://github.com/ipfs/js-ipfs-api/issues/797

ipfs / in-web-browsers