3 Replies Latest reply on Aug 6, 2010 4:04 PM by PHRED-SE

    What are the required settings to enable HTTP Compression?


      I am running into download speed issues with some of my clients.  I am looking for ways to improve download response without having to rewrite my system(s).


      On the server side, I am using CF 8.01 on a W2003 system.  I have enable HTTP Compression for the web site in IIS 6.0 for both static and dynamic files.


      On the client side where I am doing my testing, I am using IE 8.0 on a W7 professional system.  In I.E., I have enabled HTTP 1.1 under advanced options and am using Automatic mode as the download methodology for Temporary Files.


      It is my understanding that there is nothing that I have to do to CF to enable HTTP Compression.


      It does not appear to work because the downloaded cfm files (5717 and 694389) are the same size regardless of these setting.  In addition, I am using HttpWatch to determine all of the time and size parameters for each request. HttpWatch tells me in the summary that there are no HTTP Compression savings; i.e., HTTP Compression saving: 0 bytes.  Based upon some of the info I've read on the web, I would have expected 50% to 75% savings since the two files being downloaded are both dynamic text files.  All of the graphics, javascript, css files are cached so they do not figure into the equation.


      Is there something else beyond the IIS and IE settings that needs to be done to implement HTTP Compresssion???


      Thanks in advance for your suggestions/help.