Why does Google Chrome Frame not add its supported MIME types (such as application/chromeframe) to the HTTP Accept header?
In almost all cases, browsers (including Internet Explorer) include a */* entry in their Accepts header, which means that all MIME types are accepted and that any additional MIME type supported by Google Chrome Frame is covered by that entry even though it’s not explicitly mentioned. Here’s a blog post with more information.