IIS 7 and Above
IIS 8.5 Static Compression
Last post Oct 09, 2017 07:12 AM by Yuk Ding
Oct 06, 2017 02:47 PM|AWSAlan|LINK
Are there any undocumented rules that IIS uses to determine whether to serve a compressed static file or the original?
We have some CSS & JS files that are being accessed tens of thousands of times per day and these are being served gzipped. We have some other files that are probably only being accessed a few hundred times a day and they are not.
The IIS Temporary Compressed Files folder does contain the files that are not being served zipped. So IIS
has compressed them but is simply choosing not to serve the compressed versions.
I have a hunch that this might be something to do with either:
We are using the default settings, only compress files over 2.7Kb and only use 100 Mb of storage. Current used storage is 1.7Mb and the files in question (a mix of CSS and JS) are 600 or so KB.
Bit of a head-scratcher this one.
Oct 06, 2017 03:03 PM|AWSAlan|LINK
A colleague has pointed me in this direction...
The default is 2 hits in 10 seconds.
Case closed I think.
Oct 07, 2017 01:14 AM|Rovastar|LINK
Yes that is likely the case.
Here are some more details:
Oct 09, 2017 07:12 AM|Yuk Ding|LINK
Rovastar's link show that if you need to compress for each request, just set frequentHitThreshold to 1 in serverruntime. It will be appreciated if you could mark your own reply or rovastar's reply as answer. So that this thread could help more people who
have trouble in httpcompression.