# Bad value “Content-Script-Type” for attribute “http-equiv” on element “meta”.
> Canonical HTML version: https://rocketvalidator.com/html-validation/bad-value-content-script-type-for-attribute-http-equiv-on-element-meta
> Attribution: Rocket Validator (https://rocketvalidator.com)
> License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/)
The `http-equiv` attribute on the `` element simulates HTTP response headers. However, the HTML living standard only allows a specific set of values for `http-equiv`, and `Content-Script-Type` is not among them. The allowed values include `content-type`, `default-style`, `refresh`, `x-ua-compatible`, and `content-security-policy`.
In HTML 4.01, `` was used to tell the browser which scripting language to assume for inline event handlers (like `onclick`). Since JavaScript is now the only scripting language supported by browsers, this declaration serves no purpose. Every modern browser already assumes JavaScript by default, making this meta tag completely redundant.
Removing this tag has no effect on your page's behavior. Your scripts will continue to work exactly as before. If you're maintaining a legacy codebase, you can safely delete this line during any cleanup or modernization effort.
## Examples
### ❌ Invalid: using `Content-Script-Type`
```html
My Page
```
This triggers the validation error because `Content-Script-Type` is not a valid `http-equiv` value in modern HTML.
### ✅ Fixed: remove the obsolete meta tag
```html
My Page
```
Simply remove the `` line. No replacement is needed — browsers already default to JavaScript for all script handling.
### ✅ Valid `http-equiv` values for reference
Here are some examples of `http-equiv` values that *are* valid in modern HTML:
```html
My Page
```