Viewing 1 replies (of 1 total)
  • Plugin Author Dimitar Ivanov

    (@zinoui)

    Hi @martychc23,

    It’s true that the “chrome=1” isn’t a standard flag in “X-UA-Compatible” header, and that’s the reason the REDbot and W3C validator to show a warning about it.

    Despite the fact noted above the chrome flag specifies that Google Chrome frame should start if the user has it installed.

    In short, it has a purpose of having it.

    P.S. Setting up this header throughout the HTTP Headers plugin gives you a choice to use the chrome flag or not.

Viewing 1 replies (of 1 total)
  • The topic ‘The X-UA-Compatible header’s syntax isn’t valid.’ is closed to new replies.