https://man.liquidfiles.com
LiquidFiles Documentation

The LiquidFiles appliance pushes some boundaries of what’s possible with browsers. In general, we support the two most recent major releases of four most popular browsers.

Please see the matrix below for different browser versions and their limitations:

BrowserUpload MechanismMax DownloadMax Upload
Internet Explorer 11 HTML5 No Limit No Limit
Internet Explorer 10 HTML5 No Limit No Limit
Internet Explorer 9 Legacy3 No Limit 4 Gb
Internet Explorer 8 (limited support4) Legacy3 No Limit 2 Gb
Chrome1 HTML5 No Limit No Limit
Firefox2 HTML5 No Limit No Limit
Safari 7 HTML5 No Limit No Limit
Safari 6 HTML5 No Limit No Limit

1) Chrome is auto updating. We are assuming that you are running the latest release, although you can use any version that has HTML5 File.API support (we haven't tested specifically but you'll probably be safe from version 13 or 14).
2) Firefox is auto updating and we assume you're running the latest version, although you use any version from version 14 and above. While technically Firefox has supported the HTML5 File.API from version 3.6, until version 14 there was a bug in the function that splits the file into smaller parts and Firefox would load the entire file into its memory and would crash if it didn't have enough memory so effectively sending multi GB files didn't work properly.
3) With HTML5 compliant upload mechanism, files are uploaded when they are selected. With Legacy Upload mechanism, files are uploaded during send, i.e. files will start to upload when you hit the send button. 
4) Internet Explorer 8 is getting old and a few underlying libraries have stopped supporting IE8 (as of LiquidFiles v2.5). We will still make sure that base functionality in IE8 is working but will make no attempts to add functionality that is available in modern browser to IE8.

LiquidFiles will automatically detect the presence of the HTML5 File.API needed to send files with unlimited file size. While there is some support for HTML5 in IE9, it doesn't support the File.API. IE10 is the first browser to support the HTML5 File.API.

The Send limitations are limitations in each browser. It’s not possible to “fix” Internet Explorer 8 or 9 to send a 8Gb file, these are the inherit limits of those browsers.

The problem is compounded with a sort of - how do we describe 30 hours on a 12 hour clock? 2 revolutions and 6 o'clock. But since the equivalent of revolutions doesn't exists, all we're left with is 6 o'clock, or back in computer land - a 5 Gb file uploaded in IE9 will be uploaded as a 1Gb file. It just "turns over" every 4Gb. The following message is shown if someone has a setting that would allow them to upload a larger file, but their browser prevents them:

images/general/internal_external/filesize_limit.png

Since we cannot detect properly in this case if someone have selected a larger than 4Gb file, this is so far the best we can do, and probably the way it's going to stay until IE 11 or 12 when we can (finally) end support for the non HTML5 compliant versions of Internet Explorer.

Comments