← Back to release summary

Content-Security-Policy delivery via response headers for dedicated workers.

Category
Security
Type
No developer-visible change
Status
Enabled by default (Chrome 97)
Intent stage
Shipped

WPT details: https://wpt.fyi/results/content-security-policy/inside-worker?label=experimental&label=master&aligned Some tests inside WPT are still testing the old chrome behaviour. They will be fixed as part of this.

Summary

Dedicated workers should be governed by the Content Security Policy delivered in their script response headers. Chrome incorrectly used to instead apply the Content Security Policy of the owner document. We would like to change chrome's behaviour to adhere to what is specified.

Motivation

This is sort of a bugfix. We'd like to change chrome's behaviour to adhere to what was agreed on the specification and what other vendors (Firefox mainly) already implement.

Standards & signals

Ecosystem

View on chromestatus.com