Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm facing the problem that our lengthy CSS file (129 KB) gets delivered by our ASP.NET web app (running on IIS 7.5 using .NET 4.0) compressed to 24 KB on my local server machine and 36 KB on both our staging and production sites. My local OS is Windows Server 2008 R2 Enterprise, the web servers run Windows Web Server 2008 R2.

I used the Fiddler to look into the requests but they seem not to differ in anything important, i.e. Accept-Encoding: gzip, deflate is sent to all servers and all reply with Content-Encoding: gzip. All have static and dynamic compression enabled.

Does anybody have any idea what could be causing the difference in behavior?

share|improve this question
up vote 2 down vote accepted

Check out Scott Forsyth's blog entry on compression... it's a great one. Most importantly, there are several compression levels that can be set and may be different between your servers. You can check out more at the site on httpCompression.


share|improve this answer
Thanks, I wasn't aware of the different compression levels! Will check it out in detail but for now your answer put me on the right track, I guess. – Oliver May 11 '12 at 1:14

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.