Missing Content Type HTTP header

Documentos > Datadog Security > OOTB Rules > Missing Content Type HTTP header

This page is not yet available in Spanish. We are working on its translation.
If you have any questions or feedback about our current translation project, feel free to reach out to us!

Description

This publicly exposed API endpoint does not implement the Content-Type and X-Content-Type-Options HTTP headers. These headers declare the resource’s media type, preventing browsers from performing MIME type sniffing. Without the headers, browsers may interpret the content in unexpected ways.

Remediation

Implement the Content-Type HTTP header with the appropriate value.
Example header value:
```
Content-Type: application/json; charset=utf-8
```
Add the X-Content-Type-Options header with the “nosniff” value to prevent MIME type sniffing.
Example header value:
```
X-Content-Type-Options: nosniff
```