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.

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

Parse and ignore Structured Header parameters in COEP and COOP #5220

Closed
zcorpan opened this issue Jan 20, 2020 · 2 comments
Closed

Parse and ignore Structured Header parameters in COEP and COOP #5220

zcorpan opened this issue Jan 20, 2020 · 2 comments
Labels
topic: cross-origin-embedder-policy Issues and ideas around the new "require CORP for subresource requests and frames and etc" proposal topic: cross-origin-opener-policy Issues and ideas around the new "inverse of rel=noopener" header

Comments

@zcorpan
Copy link
Member

zcorpan commented Jan 20, 2020

See WICG/cross-origin-embedder-policy#2

Once Structured Headers is more stable, the COEP and COOP headers should be parsed as SH "item", and unknown parameters should be ignored (without ignoring the entire value).

Currently, COOP is specified as comparing the whole value, and COEP (as of WICG/cross-origin-embedder-policy#2 ) is specified in terms of SH but any parameter causes the entire value to be ignored. (I believe these two are equivalent.)

cc @annevk @domenic @mikewest @mnot

@zcorpan zcorpan added topic: cross-origin-opener-policy Issues and ideas around the new "inverse of rel=noopener" header topic: cross-origin-embedder-policy Issues and ideas around the new "require CORP for subresource requests and frames and etc" proposal labels Jan 20, 2020
@zcorpan
Copy link
Member Author

zcorpan commented Jan 20, 2020

Hmmm. Maybe this is actually a duplicate of #5172

@annevk
Copy link
Member

annevk commented Jan 20, 2020

Yeah, let's not add another place to discuss this.

@annevk annevk closed this as completed Jan 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic: cross-origin-embedder-policy Issues and ideas around the new "require CORP for subresource requests and frames and etc" proposal topic: cross-origin-opener-policy Issues and ideas around the new "inverse of rel=noopener" header
Development

No branches or pull requests

2 participants