[Feature Request] Replace mg_http_upload by TUS

[Lohann]

Environment

• mongoose version: 7.18
• Target hardware/board: any

Thank you for maintaining this awesome library, I have a feature request regarding uploading files greater than MG_MAX_RECV_SIZE bytes.

Request

Currently for uploading big files, mongoose suggests using mg_http_upload function, which is very limited:

• Doesn't support custom HEADERS in the response, such as CORS necessary to upload files from webpages hosted in a different host.
• Doesn't provide a way to know the total file size, consequently is not possible to known when the upload finished.
• There's no way for the user retrieve the MG_MAX_RECV_SIZE to know the maximum chunk size, neither the offset in case he lost track of it.
• Non-standard, front-end is forced to implement custom javascript code for upload files, instead of using existing solutions such https://github.com/transloadit/uppy

TUS

A more standard way for uploading big files is using TUS - Open Protocol for Resumable File Uploads, which is currently a very adopted standard for upload big files in chunks, it uses headers instead of query variables.

References:

• Website: https://tus.io/
• Specification: https://tus.io/protocols/resumable-upload#core-protocol
• Rust Implementation: https://github.com/s3rius/rustus/tree/master/src/protocol (I haven't find a C implementation yet).

[scaprile]

Your feature request is not a Mongoose issue, please do not open an issue to request a feature, particularly when there is a place for feature requests. Moved there

[scaprile]

Mongoose is embedded oriented, microcontrollers, not server oriented. It is not meant to be a file transfer engine, it just needs to be able to support a file transfer that can provide an OTA firmware upload.

Said that,
please see our tutorials and examples, we have file transfer examples able to send any file length
MG_MAX_RECV_SIZE is a constant, you can work your way to serve it to your client with a query or as an SSI, if you want that
total file size is known via content length, unless you want to do partial uploads.
mg_upload() is just one more tool of the trade.

[scaprile]

I you have a commercial application for this, please contact Support to discuss your use case and licensing. Thank you