I haven’t played with XP Service Pack 2 yet due to not having ready access to a Windows smachine that I can upgrade, but it seems that one of the security changes made to IE has greatly increased the importance of serving up the correct Content-Type header. Aldo Hoebon writes about this in HTC components in XP Service Pack 2, and describes how the wrong Content-Type for a proprietary IE HTC file (as seen in the alpha-transparent PNG fix for that browser) can cause the HTC file to have no effect.
Related posts:
- Streamy Goes Public With Advanced Social News Service Users of the Streamy service can create profiles, join groups,...
- Customer Service 101: The Customer’s Perspective Sometimes personal experiences can provide valuable business lessons. Alyssa shares...
- How to Use Twitter for Customer Service One of the greatest ways businesses can use Twitter is...
- How Zappos Does Customer Service and Company Culture At the recent SxSW conference, Matt Mickiewicz was fortunate enough...
- Codebase Launches Git-based Project Management Service Codebase, a new web application for web developers that launched...
Nice one, never knew that. HTC is not really standard anyhow, so thats not too much of a problem:)
November 30th, 2004 at 8:44 am
It’s important however, since HTCs are used for the IE7 project, to name a famous example.
November 30th, 2004 at 3:30 pm
Yeah leaned all about this the hard way. Problem is that IIS on SP2′d systems or on Win2k3 will not serve files it doesn’t recognise.
We had this with .VBD files (the old way of running VB apps inside IE)you need to add a mime type for the file you wish to serve ( and in some cases you need to reboot the server)or you’ll get a 404 error…
Theres info on this at http://www.wwwcoder.com/main/Default.aspx?tabid=68&mid=407&site=1880&parentid=170
December 8th, 2004 at 7:48 am
Just because that the IE7 project uses it doesn’t really make it important. If you want fabulous designs, and want to make the design world a better place, stick with standards.
December 8th, 2004 at 9:43 am
I think webgodjj may be thinking of Microsoft’s next IE — the IE7 project (http://dean.edwards.name/IE7) is specifically useful because it allows you to code to standards and still get IE5+ to recognize your code. Without IE7, I’d have all sorts of CSS hacks throughout my stylesheets in order to make IE comply. CSS hacks may seem like standards, but until they standardize the bugs the hacks rely on I try to stay away.
December 8th, 2004 at 1:26 pm
I’m as big a pusher of standards (and firefox ;-) as they come, but in a commercial situation where you’ve got a CMS built for IE6 only, written mostly with .HTC files, this WAS really important. For some of us it’s got to do with money and functionality, not design. In my opinion Microsoft stuffed up by burning the very people they enticed into their new technology years ago.
So thanks a lot for the info – much appreciated.
December 8th, 2004 at 6:20 pm
IE7 no longer uses HTCs. It is now a pure JavaScript solution. Some developers did not have access to their servers and could not make the necessary configurations there.
December 11th, 2004 at 9:15 am