I've only had this script for a few days....but...I was able to solve this issue on a windows server...haven't had a change to do any testing on a Linux server yet but I will post again when I have. With the settings below I am able to upload files in excess of 1.5GB.
1.) php.ini needs to have the following entries:
post_max_size = 2001M
upload_max_filesize = 2000M
max_execution_time = 86400
max_input_time = 86400
memory_limit = 2048M
These values seem extremely high...I know...but during stress testing (uploading 650 x 1.5GB files simultaneously from many remote clients) I found that these were the best values for perfect performance. The reason they are high is due to the fact that not everyone will have consistent and steady upload streams and the script has to run for each session of client side upload for the length of the upload.
2.) In the root folder of the DFH website you should see a file called "web.config" in this file you need to make the following entries (you will have to merge these entries with those already there):
<?xml version="1.0" encoding="UTF-8"?>
<configuration>
<system.webServer>
<staticContent>
<clientCache cacheControlMode="UseMaxAge" cacheControlMaxAge="100.00:00:00" />
</staticContent>
<urlCompression doStaticCompression="true" />
<security>
<requestFiltering>
<requestLimits maxAllowedContentLength="2147483648" />
</requestFiltering>
</security>
</system.webServer>
</configuration>
The main problem is that by default IIS (windows webserver) has default settings which restrict client side upload values to about 4MB which can be slightly increased from server side scripts, apps, etc., however php does not currently have the ability to override this setting to great excess. The settings added to the web.config file allow for content to be cached and static content to be compressed as well as force IIS to allow uploads of 2GB. If you want to upload files larger than 2GB we would need to add some more "stuff" to the DFH scripts to allow for file chunk uploads and a server side recompile of the file. I can assist in this matter if anyone really REALLY needs to upload larger than 2GB.
*** I just noticed in a preview of this post that my entries for web.config file are not indenting the way I typed it so you will have to match the indentations to the web.config file you are merging them with *** However it has been my experience that the indentation doesn't matter, this statement is for anyone who notices it isn't indented the way their web.config file is.
3.) The next major step is to verify that you have keep alive in your firewall set to allow for the session length needed to accommodate for the time it will take a remote user to upload a file of this size. This setting will vary greatly depending on your internet pipe. Mine being a 10Gbps connection I have adjusted my keep alive settings accordingly and I suggest you look up the best keep alive settings for your pipe range.
On a side note if someone has access to a Linux server with DFH on it that I could conduct the tests to find the root of the problem let me know. I think it is called PM? Yeah PM me.