Open
Description
This a a meta-issue tracking known issues and ongoing improvements related to uploads of big (1GB+) files in web browser contexts.
Known Problems with HTTP API
Invalid progress reporting:
- Streaming versions of ipfs.files.add buffer entire data in memory before doing HTTP POST
- Chromium crash when sending <200MB over js-ipfs-api
- IN PROGRESS waiting for release with upstream fix to
stream-http: fix: fix >150mb bodies from crashing jhiesey/stream-http#93 - related issues
- crash when dropping a big file (crash when dropping a big file ipfs-companion#464)
- Uploading big files crush page in Chrome (Uploading big files crush page in Chrome ipfs-inactive/js-ipfs-http-client#654)
- upload-file-via-browser can only upload file size less than 165MB (upload-file-via-browser can only upload file size less than 165MB ipfs-inactive/js-ipfs-http-client#788)
- IN PROGRESS waiting for release with upstream fix to
- Silent crash in Firefox when Buffer max size is breached:
- upstream issue: crash when dropping a big file ipfs-companion#464
- IN PROGRESS waiting for release with upstream fix to
stream-http: fix: fix >150mb bodies from crashing jhiesey/stream-http#93
- IN PROGRESS waiting for release with upstream fix to
- upstream issue: crash when dropping a big file ipfs-companion#464
- Silent error while files.add over HTTP API (
http: invalid Read on closed Body)- go-ipfs: Error while files.add over HTTP API (http: invalid Read on closed Body) kubo#5168 (should land in go-ipfs v0.4.19 - Error while files.add over HTTP API (http: invalid Read on closed Body) kubo#5168 (comment))
- js-ipfs-api: https://github.com/ipfs/js-ipfs-api/issues/797
Ongoing Work
- Fix to
stream-httpis ready, waiting to be released: fix: fix >150mb bodies from crashing jhiesey/stream-http#93 - Add support for chunked uploads to
ipfs.add([WIP] feat: add support for chunked uploads ipfs-inactive/js-ipfs-http-client#851 | [WIP] feat: support chunked add requests js-ipfs#1540 | go-ipfs/?)