large static file downloads stop at 50MB

[mblyman]

I am currently have a host that is using litespeed and I am getting an issue when downloading large static files.

The download of any file stops at 50 MB regardless of the file size. Some are 52 MB others 80 MB and no matter the original size it stops at 50 MB as if it had completed the download without any errors.

Of course if I try to open the file it is corrupt because it didn't completely download.

I'm using Magento ecommerce to run digital download products and this is where the issue I believe it happening is with litespeed and perhaps some configuration setting.

I have two different servers, one is running apache and then one running litespeed. Only the litespeed server is causing issues with the digital downloadable products in magento.

If it helps the downloads are all via https rather then http.

Has anyone heard of this issue before?

Thanks

Mike

 

[auser]

there is a setting for "Max Dynamic Response Body Size":
http://www.litespeedtech.com/docs/webserver/config/tuning/#maxDynRespSize

but looks no limit for static file size?

 

[Bono]

My users complain about that too, sometimes it breaks really fast, and sometimes near the end.

I have tried just now, size of the file 58MB, it broke at 10MB.

Second try, same file in IE 8 it broke at 48MB.

Hmm after five tried it looks like that it usually brakes at 10.02MB.

 

[anewday]

All all these files served through PHP?

 

[Bono]

All all these files served through PHP?

Yes, though download interface called DOCman, http://extensions.joomla.org/extensions/82/details

 

[mblyman]

To help coordinate efforts on this issue here is the link to the thread on the magento forums.

http://www.magentocommerce.com/boards/viewthread/41264/

based on what is being said it appears that it is a litespeed issue rather then application issue like magento or joomla or other 3rd party scripts used for downloading files.

 

[mblyman]

@Bono

All the files in magento commerce are served through PHP as well

 

[auser]

I took a quick look at DOCman source code, the downloaded file is sent to user by .php, so its size is limited by "Max Dynamic Response Body Size" I mentioned in previous post. try to increase it to 100M/200M and see how it goes.

to compare with pure static file download, you can put a large file, say aaa.tar(80M) at document root, and access it by direct link http://www.yourdomain.com/aaa.tar, see if the file can be downloaded completely.

 

[Bono]

I took a quick look at DOCman source code, the downloaded file is sent to user by .php, so its size is limited by "Max Dynamic Response Body Size" I mentioned in previous post. try to increase it to 100M/200M and see how it goes.

to compare with pure static file download, you can put a large file, say aaa.tar(80M) at document root, and access it by direct link http://www.yourdomain.com/aaa.tar, see if the file can be downloaded completely.

Very nice, I used 100MB and my downloads are fixed. My biggest file is only 80MB big so 100MB will be more than enough.

Funny thing was I had error msg in LSWS control panel but I thought it is error from my web gallery.

"The size of dynamic response body is over the limit, abort!"

 

[mistwang]

It will be much more efficient if DOCman can use "Internal redirect" instead of streaming the file through PHP.

http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed:wiki:feature:internal_redirect

Just test if it is a LiteSpeed Web Server, send back a "X-LiteSpeed-Location: ..."

 

[Bono]

It will be much more efficient if DOCman can use "Internal redirect" instead of streaming the file through PHP.

http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed:wiki:feature:internal_redirect

Just test if it is a LiteSpeed Web Server, send back a "X-LiteSpeed-Location: ..."

You are right, that would be more efficient way but since that site is low profile it can stay like this. If it was high profile site, it would really soon eat up all the memory. Maybe in new version of DOCman that is fixed, but I'm still using older version.

Thanks

 

[mblyman]

My host fixed it as well and here is what they said about the setting they changed.

“It was a setting for litespeed under I believe it was “Tuning” for “max post size” was 50M set this to 1000M (the max)

I'm not sure if this is the same or something different then the setting referenced earlier in the post

 

[Bono]

They used that option, but if you do not have files close to 1GB, that setting is overkill.

 

[auser]

My host fixed it as well and here is what they said about the setting they changed.

“It was a setting for litespeed under I believe it was “Tuning” for “max post size” was 50M set this to 1000M (the max)

I'm not sure if this is the same or something different then the setting referenced earlier in the post

"max post size" should be "Max Dynamic Response Body Size (bytes)" referred in this thread.
It's quite reasonable to increase it to resolve the issue.