March 5th, 2008
March 4th, 2008
Continuing from previous post
Following are the web log entries that contain the new MSIE 8.0 user agent string, with the specific MS IP address blocked out:
—-.microsoft.com - - [04/Mar/2008:01:55:29 +0000] "GET /favicon.ico HTTP/1.1" 200 1406 "-" "Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.0; SLCC1; .NET CLR 2.0.50727; .NET CLR 3.0.04506; .NET CLR 1.1.4322; InfoPath.2; .NET CLR 3.5.21022; MS-RTC LM 8; OfficeLiveConnector.1.0)"
—-.microsoft.com - - [04/Mar/2008:01:55:29 +0000] "GET /standards/ie8-standards-mode-by-default/ HTTP/1.1" 200 29177 "http://www.techmeme.com/" "Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.0; SLCC1; .NET CLR 2.0.50727; .NET CLR 3.0.04506; .NET CLR 1.1.4322; InfoPath.2; .NET CLR 3.5.21022; MS-RTC LM 8; OfficeLiveConnector.1.0)"
Typically, IE access to this site results in only one log entry: the entry for the specific page. There are no log entries for CSS files, JS files, and so on, because IE doesn't support the XHTML MIME type, and therefore doesn't parse the page and pull these resources. This is what I'm seeing in my web log for these log entries.
These two log entries also reflect the new Office Live functionality, just released. The Office Live functionality could impact on what's picked up from a page–hard to say, because I don't have any Office Live accesses for my sites that aren't strict XHTML. However, if these log entries do reflect access of the post directly with IE8, based on the fact that none of the CSS or image files were also pulled, and based on the pattern of access of pages at this site by previous versions of IE, IE8 does not support the XHTML mime type.
To repeat what I said in the last post, this statement isn't based on a confirmation from the company. It's a guess based on current web log entries reflecting the new user agent string for IE8, an IP address that resolves to inside Microsoft, and matching a pattern I've seen with previous IE versions that cannot access this site because of the MIME type I use. With the continued silence from the IE team and Microsoft, guesswork is all I have to go on. I sincerely hope I'm proven wrong.
March 3rd, 2008
Others might talk about Microsoft's move to the clouds, but one decision MS made shows its feet are firmly planted on solid ground: IE8 will be standards mode by default.
This was a good decision, but it's also an ominous decision. Not a word on support for the XHTML mime type. With no clear idea of exactly what MS has planned for this release, I am forced to hold my huzzahs until we see what IE8 actually delivers. According to the ieblog report, IE8 will be one of the topics covered at MIX08. Perhaps we'll see the first beta release of IE8 this week.
To put this in perspective, Microsoft has just agreed to deliver what Opera, Firefox, and Safari have always delivered.
update One interesting thing about this announcement–the IE program manager announced the move on the ieblog, and Ray Ozzie announced it in the press release. Where's Chris Wilson?
second update Jeffrey Zeldman sounds like a man who put himself on a line that just disappeared.
third update I just sent an email off asking the opinion of someone who knows this stuff better than me what he thinks, but from web log entries for this site, based on the new MSIE 8.0 user agent string, IE8 does not support the XHTML mime type. I repeat: IE8 does not support pages served up with application/xhtml+xml.
Again, this statement isn't based on a confirmation from the company. It's a guess based on current web log entries reflecting the new user agent string for IE8, and matching a pattern I've seen with previous IE versions that cannot access this site because of the MIME type I use. I sincerely hope I'm proven wrong.
