Generate And Incrementally Stream A ZIP Archive File On-The-Fly In Lucee CFML 5.3.7.47

Hey Ben. This is a great article. At the moment, I am building a project that requires a file upload of 20MB+

I am using the latest version of Lucee on Windows 2012R2 with IIS7

After about 5 minutes, the connection drops. No CF or IIS error.

I have set the:

<cfsetting requestTimeOut="1000" />

My form has the following set:

enctype="multipart/form-data"

I have set the following in my web.config:

<system.web>
	<httpRuntime maxRequestLength="25480" />
</system.web>

I have also made sure I have set the correct folder read/write permissions, for the upload, on my VPS.

I am racking my brains but cannot think of anything obvious, I am missing. I must say, I have never tried to upload files of more than 5MB, in the past, but 20MB, doesn't seems that excessive.

Any ideas?

Just one small, amendment. My Lucee version is 5.3.6.061

Ben. Thanks for all your suggestions. I will check out the content-length header.

I have now found that anything below 4MB, uploads fine and interestingly, the default web.config:

maxRequestLength

Is 4MB

Now earlier I set ** maxRequestLength** to 102400, thinking that this setting was in KB, but, in fact, I have found out that in IIS6, it is in bytes. So, I am going to bump this up to 102400000, and see what happens!

I thought I was using IIS7, but in fact, it looks like my Windows 2012R2 VPS is running IIS6, which is a little strange.

Sorry. It is IIS8, not IIS6. Just double checked. So, I read a very interesting article about the difference between IIS6 & 7, which probably means 8, as well!

https://weblogs.asp.net/jeffwids/from-iis6-maxrequestlength-to-iis7-maxallowedcontentlengthfile-specifying-maximum-file-upload-size

It seems I need to use maxAllowedContentLength instead of maxRequestLength, but the latter seems to override the former, if both are set in IIS8.

Anyway, enough talk, it is time to find out whether my hypothesis works!

I shall let you know the outcome, in case you ever come across this problem, in future.

Hi Ben. Wow. I have cracked it!

Not quite, how I explained in the previous reply.

In the end, I had to add both maxAllowedContentLength and maxRequestLength, like:

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
    <system.webServer>
...
		<security>
			<requestFiltering>
				<requestLimits maxQueryString="32768" maxAllowedContentLength="104857600" />
			</requestFiltering>
		</security>
    </system.webServer>
	<system.web>
       <customErrors mode="Off" />
	   <httpRuntime maxRequestLength="102400000" />
	</system.web>
</configuration>

It seems that both attributes are in bytes, not kilobytes.

That just wasted a whole day, but it is well worth knowing, in case, I need to add capacity for big file uploads, in future.

One last thing, that I overlooked.

In my last reply, I only tested a 10MB file. I decided to test my target file which is just shy of 20MB. I got a new IIS error. Something about Application Timeout?

But, with a quick look on StackOverflow, I found an easy solution. We just have to add the following attribute to the web.config httpRuntime property:

executionTimeout="3600"

This adds a 60 minute timeout for any page request.

My final web.config without the guff:

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
    <system.webServer>
...
        <security>
            <requestFiltering>
                <requestLimits maxQueryString="32768" maxAllowedContentLength="104857600" />
            </requestFiltering>
        </security>
    </system.webServer>
    <system.web>
        <httpRuntime maxRequestLength="102400000" executionTimeout="3600" />
    </system.web>
</configuration>

The executionTimeout attribute uses a value in seconds.

With this set-up, we can now upload files up to about 100MB. Hooray.

My apologies for hijacking your blog with an unrelated topic, but hopefully, this might help someone, in future.

Ben. As regards your database issue, there are so many settings that we are often unaware of, but it is actually quite satisfying, getting to the bottom of each problem.

I will remember this because I am certain, I will need to submit larger data packets to my MySQL database, at some point, in the future.
64KB seems pretty small to me, but I am sure there is a good reason for this.

Thanks for the heads up!

I must say, I am amazed that some of these default values are set so low. Only 4MB upload limit on IIS8. Lucee/Tomcat is 50MB, which seems reasonable I realise that normally, people upload small images etc, but 4MB, seems a bit low? And 64KB for a MySQL packet seems kind of small.

I am just amazed that I have never come up against these limits before, in my 20 year career as a technical developer.

We live & learn...