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?
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 IIS.net site on httpCompression.
- How to make some virtual folders be served by iis while others are served by apache?
- IIS Web Farm Framework servers are automatically set to “unavailable” even when they are healthy… And they never return to the available state!
- HTTP Compression on IIS 6.0 (Windows Server 2003)
- Limiting File Types Logged by IIS (Reducing Log File Size)
- Strange Problems with IIS Servers hanging for some clients