IE11 no longer identifies itself
I haven't seen this picked up elsewhere, so I thought I'd point it out. In earlier Windows previews, IE11 had supposedly switched to using "IE 11.0" in the user agent string instead of "MSIE 11.0" in order to break most current browser detection and have sites deliver fully capable versions to the latest IEs. However, I just installed the Windows 8.1 preview, and IE11 actually gives me this as a User-Agent:
Mozilla/5.0 (Windows NT 6.3; WOW64; Trident/7.0; rv:11.0) like Gecko
Note the complete lack of "IE" or "MSIE"... if you really want to know that it's IE, you need to use the Trident string as the key indicator, I'd say, and then the "rv:" to capture the browser version.
Also, all the other major browsers (Chrome, FF, Opera) don't pick up NT 6.3 (Windows 8.1 OS) in the preview... they're all showing 6.2, while IE shows 6.3.
No idea if that's the ultimate agent that will go out with the full release of 8.1, obviously.
4 comments
[ 3.2 ms ] story [ 19.3 ms ] threadIf Microsoft want's IE11 to be taken seriously, I think they've played their cards properly, as this should bypass existing IE filters. It somewhat feels like "deception" (Microsoft trying to fool the Web), but in their defense, the IE filters out there are not discerning enough -- somebody couldn't get their site to work in IE8, so they blocked ALL IE. There's no way Microsoft can combat this other than this tactic.
Now, if IE11 fails to deliver, I think they will only make the situation worse, as people will start building Trident filters.
It is the same situation with hiding support for things like document.all, so they avoid the sniffers that do: if (document.all) { ie = true; } then use the ie variable to give those browsers the legacy IE code path.