The reason to worry about these problems is that the built-in functions within dotNET for handling file uploads in IIS in ASP.NET are written to cache the entire file upload to memory before streaming the file to disk. Therefore, if you allow very large file downloads, you run the risk of letting someone perform a denial of service attack on your IIS server because all it takes is an explosion of several very large file downloads to release the available physical memory to the server. Therefore, the answer to this question is to either write your own download handler that does not cache the entire file download into memory, or use one of the many available software components that you can install and do it for you. The other two answers indicate a pair. Here is another component I found for ASP.NET:
http://www.easyalgo.com/eaupload.aspx
dmarietta
source share