Kazusa But the upload is still limited by the server and needs to be modified together.
Yes of course, and that's the point of upload_max_filesize
, to limit upload sizes. If you need large file uploads, you need to make sure you have a server that is capable, which you can configure to accept large file uploads. This option is not meant to be bypassed.
Kazusa Also, I seem to have found a bug: when using the zip download function, you may end up with an HTML source code file called [folder.zip]. I tested the server and download on the same device, I think it has something to do with the device memory --- my computer has 16G memory taking 50%, when I download the 3Gb zip, I see that the browser memory keeps increasing and exceeds 3G, At the same time the disk is occupied. When I run out of memory, I get a 1kb zip.
There are two ways to serve zip downloads:
1. Create ZIP file on server
First create the zip file on server, then serve to client (browser). This is how it used to be done in Files gallery earlier versions. There is no way your server would be able to create a 3GB zip, unless you have a powerful dedicated server which you control ... It would timeout way before 1GB (probably even before 300 MB). Besides, creating zip on server requires storing the zip as cache on server, which would require a huge amount of additional storage.
2. Create zip in browser
Downloads files and creates zip in browser. This is how it's currently done in Files gallery. It is faster than creating zip on server, and does not require storing the cached zip on server. Also, in most cases, it can handle much larger ZIP files (relative to the device capabilities).
There are no other ways to server ZIP files to the visitor. In both cases above, there is no "magic" I can do from Files gallery to allow your devices to download massive 3GB+ zip files. Your option would be to change to server ZIP method, but this would not work any better for large zip files ... It would timeout for sure, unless you have your own powerful dedicated server. It seems you have unrealistic expectations about downloading massive ZIP files on shared servers and limited devices. I think there might even be a device limitation of 2GB.
Kazusa Also, because of the blob protocol, I can't seem to push to other download apps unless I know the name of the zip file that is not visible to this directory.
I'm actually not quite sure what you mean. The download is created and triggered from Javascript yes, and it's not a pre-created file on the website that other apps or browser extensions can target. You can change config option download_dir to zip
and the zip will get created on server ... However, it's unlikely your server is capable of creating a 3GB zip file without timeout error ... even if it is, it would take at least a minute or so to create the zip file before the download even starts.