Question: We are running Windows 2008 Enterprise 32-bit on vmware using IIS 7. We have installed Static Content Compression but not Dynamic Content Compression.
First we can't find were to see the min and max settings for (Only compress files larger than (in bytes)) Also which settings would you recommend? (Google says, they recommend a minimum range between 150 and 1000 bytes) is this a good range?
Second it seems to be working except it won't compress .js files. (According to https://developers.google.
Third is it neccery to install Dynamic Content Compression or is Static Content Compression enough?
Thanks
My Reply : Well Dynamic content compression is a feature which you could try to use but in corporate env, you should not use it because it delay the site reply on user end, because dynamic content takes time to unfold at user end and that could cause slowness on a busy env.
To implement compression:
Go to IIS -> Site level -> In feature view -> Compression -> Select "Enable dynamic content compression" and Apply
MinFileSizeForComp - Min 256 kbytes
CacheControlHeader value -> max-age=86400 (To enable this setting, you must set the SendCacheHeaders property to true. )
probably it may help you
My reply
The code should be :
--OR --
These both elements are defining client Cache and using Max-Age we are specifying the time lime limit but with "UseMaxage" , we are leaving it to remain there .. You may select one of them as per your requirement .
First we can't find were to see the min and max settings for (Only compress files larger than (in bytes)) Also which settings would you recommend? (Google says, they recommend a minimum range between 150 and 1000 bytes) is this a good range?
Second it seems to be working except it won't compress .js files. (According to https://developers.google.
Third is it neccery to install Dynamic Content Compression or is Static Content Compression enough?
Thanks
My Reply : Well Dynamic content compression is a feature which you could try to use but in corporate env, you should not use it because it delay the site reply on user end, because dynamic content takes time to unfold at user end and that could cause slowness on a busy env.
To implement compression:
Go to IIS -> Site level -> In feature view -> Compression -> Select "Enable dynamic content compression" and Apply
MinFileSizeForComp - Min 256 kbytes
CacheControlHeader value -> max-age=86400 (To enable this setting, you must set the SendCacheHeaders property to true. )
probably it may help you
Would it be OK to add this to applicationHost.config to work globally instead of web.config for each web server?
My reply
The code should be :
--OR --
These both elements are defining client Cache and using Max-Age we are specifying the time lime limit but with "UseMaxage" , we are leaving it to remain there .. You may select one of them as per your requirement .
