Subject: draft-ietf-httpbis-bcp56bis-11, "4.13. Co-Existing with Web Browsing"

From: Julian Reschke <[email-masked]>
Date: Mon, 5 Apr 2021 18:43:07 +0200

> An example of a HTTP response from an application that does not intend for its content to be treated as active by browsers might look like this:
>
> HTTP/1.1 200 OK
> Content-Type: application/example+json
> X-Content-Type-Options: nosniff
> Content-Security-Policy: default-src 'none'
> Cache-Control: max-age=3600
> Referrer-Policy: no-referrer
>
> [content]
>
> If an application has browser compatibility as a goal, client interaction ought to be defined in terms

In the introduction to this example, what exactly does "active" mean?

Best regards, Julian