Are there any pitfalls a person should consider before enabling HTTP Compression on IIS 6.0?
mrMister
10:40 am on Sep 14, 2007 (gmt 0)
Old browsers, (IE5 is the main culprit) have bugs in their handling of HTTP compression, so they sometimes render HTTP compressed javascript and css incorrectly.
Another issue is performance. Compressing the data requires CPU time. If your server is under high load, it may slow it down.
In general though, HTTP Compression is highly recommended.
f00sion
11:54 pm on Sep 24, 2007 (gmt 0)
I think there is also an issue with certain browsers that either don't send the correct header or are missing a header so they could be sent compressed content when the browser doesn't actually support it. The httpZip product from port80 software claims to have extra checks in there so nobody encounters any issues.
