0

Line 6, Column 66: Bad value X-UA-Compatible for attribute http-equiv on element meta.

<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">

I just cant see what is wrong,

Thanks for your time.

Cylion
  • 89
  • 7
  • Check this detail question and explanation - http://stackoverflow.com/questions/6771258/whats-the-difference-if-meta-http-equiv-x-ua-compatible-content-ie-edge-e – skool99 Sep 19 '14 at 11:01

1 Answers1

2

You can ignore this. The validator erroneously tries to map http-equiv metatags on known HTTP headers, but ignores the fact that an X- prefix indicates vendor specific extensions. This is a known issue of the validator and cannot be fixed on your end.

You could of course circumvent this by specifying it in the HTTP headers where it belongs, for example through Apache's mod_headers extensions. This requires code-level access to the site though.

Niels Keurentjes
  • 38,099
  • 7
  • 85
  • 126
  • The valdidator behavior is not erroneous. It checks according to HTML5 documents. Whether those documents have a wrong policy in this issue is a different question. – Jukka K. Korpela Sep 19 '14 at 12:37