Hi Leon,

thanks a lot for your time.

In fact my site is much smaller than 2 GB.

Also in my case the downloaded files are not empty, but just some bytes smaller than the original (wich makes them being corrupted).

I have some files in the file manager which are marked as ARSH, I deleted most of them (and the files which have download problems do not have this attribute).

I do not have any other compression module installed...

I am running DNN 4.3.5 on Windows Server 2003 and IIS 6

Hmm, really a sticky problem. Thank you again for your help!

Regards,
Fabian

---

Hi Sentry23,

Thanks again for your detailed help! Now I am sure that I have precisely the same problem as you had, because in my case, too, when I use documents smaller than 500 kb they are empty on download.

So now comes the question: I stopped html-compression... but did it really stop??? How may I check if the html-compression is still working?

Thanks again! I hope that someone of the core will take this problem in charge as it is extremely problematic: DNN without html-compression is very slow. (if someone of the core wants to check my server to understand the problem, please email me).

Regards,
Fabian

---

Hi Fabian and Damien, First of all to Fabian, you can see if you can snoop the HTTP traffic and see the data you are receiving, and if it has a gzip header in the stream, but it'll be better maybe to also check the following link first: http://technet2.microsoft.com/WindowsServer/en/library/ae342c42-fbc4-4ab7-b9ac-20a89f0fa4ad1033.mspx?mfr=true This should be a good starting point for enabling/disabling compression options (on specific paths and sites) or this link http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/502ef631-3695-4616-b268-cbe7cf1351ce.mspx?mfr=true for specific file types. This assumes you have access to the command line on the server. I really hope this helps you both further, I know at least how much I've been searching for a good solution, and still haven't come across one to enable compression again. (We're running a Intranet site with well over 700 pages, and an average of 100 authenticated users online at any time, and performance for the clients is terrible, while the server is pretty much idling).