require-sri-for
The CSP require-sri-for directive would have required Subresource Integrity on scripts and styles. Use the Integrity-Policy header instead.
Last update:
The require-sri-for Content Security Policy (CSP) directive would have forced
Subresource Integrity (SRI)
checks on scripts and stylesheets, blocking any that lacked an integrity
attribute. It never shipped to a stable browser and was abandoned.
Deprecated
require-sri-for never shipped to stable; it only ever ran behind flags. Chromium last prototyped a script-only version in early 2025, then deleted it in April 2025 because the Integrity-Policy header replaces it. Integrity-Policy shipped in Chrome 138 and is the replacement.
Use the replacement instead:
Integrity-Policy: blocked-destinations=(script)What you should do instead
Use the Integrity-Policy header, which took over the same goal: requiring SRI on the resources a page loads. The example above blocks scripts that lack integrity metadata.
Delete require-sri-for from any policy that still carries it; it has no
effect in any browser. To add the integrity attributes themselves, our
SRI guide covers the
mechanics, and the SRI generator computes the hashes
for you.
Why it was removed
require-sri-for first appeared in Chrome 54 behind the experimental web
platform features flag and never reached stable. That code was later removed. In
February 2025 Chromium revived a script-only require-sri-for 'script' behind a
flag, then removed the directive for good in April 2025 with the note that it
"is being replaced by an Integrity-Policy header". The header carries the same
goal outside CSP, with an Integrity-Policy-Report-Only variant so sites can
measure breakage before enforcing.
Browser support
No browser supports require-sri-for. It existed only behind flags, in Chrome
and for a time behind a preference in Firefox, and no browser ever enabled it by
default. Current Chrome logs
Unrecognized Content-Security-Policy directive 'require-sri-for'. and ignores
it. The
Integrity-Policy header is
the supported way to require SRI.
See also
- Integrity-Policy, the header that replaced it
- Subresource Integrity
- Directives index
- Generate SRI hashes with the SRI generator
Sources
referrer
The CSP referrer directive was a pre-CSP3 experiment for controlling the Referer header. Use the Referrer-Policy header instead.
Cross-Origin-Opener-Policy
COOP isolates your window from cross-origin openers and popups, defending against cross-window attacks and enabling cross-origin isolation.