Menu

Cross-Origin-Embedder-Policy is an isolation gate, not an origin allowlist
📰

Cross-Origin-Embedder-Policy is an isolation gate, not an origin allowlist

DEV Community: security·StarkMan·about 13 hours ago
#M7BJ5Wz1
#devtosecurity#devto#dev#origin#cross
Reading 0:00
15s threshold

Cross-Origin-Embedder-Policy is an isolation gate, not an origin allowlist

Cross-origin isolation gives a document a stronger isolation guarantee from other origins. A common deployment uses Cross-Origin-Opener-Policy: same-origin and Cross-Origin-Embedder-Policy: require-corp or credentialless . The pair changes which browsing contexts and resources can share the document's address space. It does not decide which users may access the document.

Cross-Origin-Embedder-Policy governs no-cors requests and embedded resources. With require-corp , a cross-origin resource must opt in through a compatible Cross-Origin Resource Policy or a CORS response. With credentialless , a cross-origin iframe can be loaded in a new ephemeral context without its normal credentials.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.