# X-UA-Compatible HTTP header must have the value “IE=edge”, was “IE=edge,chrome=1”.
> Canonical HTML version: https://rocketvalidator.com/html-validation/x-ua-compatible-http-header-must-have-the-value-ie-edge-was-ie-edge-chrome-1
> Attribution: Rocket Validator (https://rocketvalidator.com)
> License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/)
The `X-UA-Compatible` header tells Internet Explorer which rendering engine to use for a page. Setting it to `IE=edge` instructs IE to use the highest available standards mode, ensuring the best compatibility and avoiding legacy rendering quirks. The `,chrome=1` directive was an addition that told browsers with the Google Chrome Frame plugin installed to use Chrome's rendering engine instead of IE's. Google discontinued Chrome Frame in 2014, and the W3C validator only accepts `IE=edge` as a valid value for this header.
Including the deprecated `chrome=1` directive causes a validation error and serves no practical purpose on modern websites. No current browser recognizes or acts on it, so it's dead code that only creates noise in your markup.
The fix is straightforward: remove `,chrome=1` from the `content` attribute, leaving only `IE=edge`.
## Examples
### Incorrect
The following triggers the validation error because of the `,chrome=1` suffix:
```html
```
### Correct
Simply use `IE=edge` as the sole value:
```html
```
### Full document example
If you include this meta tag in a complete HTML document, place it early in the ``:
```html
My Web Page
Hello World
```
## Server-side configuration
If you set `X-UA-Compatible` as an HTTP response header rather than a meta tag, apply the same fix there. For example, in an Apache `.htaccess` file:
```plaintext
Header set X-UA-Compatible "IE=edge"
```
In Nginx:
```plaintext
add_header X-UA-Compatible "IE=edge";
```
## Is this meta tag still needed?
With Internet Explorer reaching end of life, the `X-UA-Compatible` meta tag itself is largely unnecessary for new projects. If your site no longer needs to support IE, you can safely remove the tag entirely. If you do keep it for legacy support, ensure the value is exactly `IE=edge` with no additional directives.