Developer forum

r.muller wrote:

hi,

 

We are running a custom application and i have a question about the HttpCompression dll that is used.

 

I am asking this because i encountered a problem when using asp.net output cache within a custom module.

 

When using asp.net output caching and when a page comes from the asp.net  outputcache i get the raw compressed output back. (which is unreadable)

When i disabled the "HttpCompression.HttpCompressionModule,HttpCompression" from the web.config the pages from the .net outputcache was returned correctly.

 

My question is can i get away with disabling the HttpCompression dll?

Second iis 6 is also applying httpcompression and works fine with the .net output cache.

Is there a reason that the dw HttpCompression dll does a better job or has other advantages that i should be aware of?

 

Best regards,

Remi

Hi Remi
 

You can disable the http cache without any impact - simply remove it from web.config. You can also specify exceptions in web.config in HttpCompressionSettings, or by adding &Compress=false to the querystring.

We have had some issues in the old days with IIS compression - can't remember what, but we have chosen this approach so we have complete control. But IIS compression should of course work.

Thank you for your quick response. I think we will remove the HttpCompression completely and rely on iis compression.