When we first started using Ajax we noticed some difficulty getting the resources to work with our HTTP compression filter. Now I have a better understanding of what issues are luring thanks to Carloc Ajax resource intermittently not accessible (http compression)
This means that Ajax does support compression for Internet Explorer 7 but it does not support compression for Internet Explorer 6. Why? Well, the fact is that IE6 has some serious troubles with compressed content, and those issues have been resolved in IE7: Internet Explorer may not decompress HTTP content when you visit a web site (scheduled for IE6 SP2) Internet Explorer does not correctly decompress data that uses the GZIP data compression method (scheduled for IE6 SP2) FIX: Internet Explorer 6 does not display the previous Web page when you browse an ASP.NET Web application and then click the Back button (scheduled for Windows XP SP3) Another release containing several fixes is in the latest Windows Script 5.7 which contains updates for jscript parser: You may experience slow performance when you view a Web page that uses JScript in Internet Explorer 6 (scheduled for WinXP SP3)
This means that Ajax does support compression for Internet Explorer 7 but it does not support compression for Internet Explorer 6. Why?
Well, the fact is that IE6 has some serious troubles with compressed content, and those issues have been resolved in IE7:
Another release containing several fixes is in the latest Windows Script 5.7 which contains updates for jscript parser:
I never realized IE6 had so many compression issues.
Remember Me
a@href@title, b, blockquote@cite, em, i, strike, strong, sub, super, u
Page rendered at Wednesday, August 27, 2008 10:30:33 PM (Pacific Standard Time, UTC-08:00)
Disclaimer The opinions expressed herein are my own personal opinions and do not represent my employer's view in anyway.