So, it appears IE8 introduced a brand new XSS protection mechanism. It apparently does so by inspecting javascript resources and modifying them before execution.

So long, so good?

Well... apparently, the "filter" is quite overzealous, and actually triggers a lot of false positives, impairing websites and legit javascript uses.

Fortunately for us, the boys anticipated their new feature to be broken, and provided a mean for everybody to actually bypass it.

Meet the "X-XSS-Protection: 0" HTTP header. Send it along your resource, and voilĂ , IE8 XSS Filter is now disabled.

From which you may obviously deduce that it's also that easy for Mr. EvilMan to workaround the "protection"...

By the way, all google websites I've checked do disable it already :-).

Same old web.

Sources:

http://michael-coates.blogspot.com/2009/07/ie-8-anti-xss-bit-overblown.html

http://msdn.microsoft.com/en-us/library/dd565647%28VS.85%29.aspx