HTTP `Cross-Origin-Opener-Policy`

Creator

Creator

Created

Created

2023 Oct 26 1:26

Editor

Editor

Edited

Edited

2023 Oct 26 1:30

Refs

Refs

HTTP Cross-Origin-Embedder-Policy

COOP


Cross-Origin-Opener-Policy: unsafe-none
Cross-Origin-Opener-Policy: same-origin-allow-popups
Cross-Origin-Opener-Policy: same-origin

Making your website "cross-origin isolated" using COOP and COEP | Articles | web.dev

Some web APIs increase the risk of side-channel attacks like Spectre. To mitigate that risk, browsers offer an opt-in-based isolated environment called cross-origin isolated. Use COOP and COEP to set up such an environment and enable powerful features like `SharedArrayBuffer`, `performance.measureUserAgentSpecificMemory()` or high resolution timer with better precision.

Making your website "cross-origin isolated" using COOP and COEP | Articles | web.dev

https://web.dev/articles/coop-coep

Cross-Origin-Opener-Policy - HTTP | MDN

The HTTP Cross-Origin-Opener-Policy (COOP) response header allows you to ensure a top-level document does not share a browsing context group with cross-origin documents.

Cross-Origin-Opener-Policy - HTTP | MDN

https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cross-Origin-Opener-Policy

Cross-Origin-Opener-Policy - HTTP | MDN

Recommendations

////////////