Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

COEP: define it as a structure header #5477

Closed
empijei opened this issue Apr 21, 2020 · 1 comment
Closed

COEP: define it as a structure header #5477

empijei opened this issue Apr 21, 2020 · 1 comment
Labels
topic: cross-origin-embedder-policy Issues and ideas around the new "require CORP for subresource requests and frames and etc" proposal

Comments

@empijei
Copy link

empijei commented Apr 21, 2020

What is discussed in #5172 similarly applies to COEP.

As per my last comment I think COEP should be specified to be a structured header to support at least report-to directives.
@annevk
Copy link
Member

annevk commented Apr 21, 2020

It already is: https://wicg.github.io/cross-origin-embedder-policy/.

@annevk annevk closed this as completed Apr 21, 2020
@annevk annevk added the topic: cross-origin-embedder-policy Issues and ideas around the new "require CORP for subresource requests and frames and etc" proposal label Apr 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
topic: cross-origin-embedder-policy Issues and ideas around the new "require CORP for subresource requests and frames and etc" proposal
Milestone
No milestone
Development

No branches or pull requests
2 participants
@empijei @annevk