Repository navigation
Add credentialless value to COEP (HTML spec) - #6638
Merged
Merged
Conversation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Originally described in: https://github.com/mikewest/credentiallessness
credentiallessandrequire-corpare similar. One or the other is a requirements for thewindow.crossOriginIsolatedcapability.They differ mostly in the fetch specification.
require-corprequires a CORP header for cross-origin no-cors responses.credentiallessdoesn't, but omits credentials (Cookies, clients certificates, etc...) in the request.HTML (Add
credentiallessvalue to COEP (HTML spec) #6638)credentiallessvalue.credentiallessandrequire-corpare equivalent. They have been grouped intocompatible with cross-origin isolationand the HTML spec rewritten to use this concept.Fetch: (Specify the behavior of
COEP: credentialless, fetch#1229)Cross-Origin-Embedder-Policy allows credentialsalgorithm. It omit credentials for no-cors, cross-origin, COEP:credentialless requests.response'srequest-include-credentialsflag.Cross-Origin-Resource-Policy check, ifembedderPolicyiscredentialless, require CORP for navigational responses, and opaque responses withrequest-include-credentials.See: #6637
At least two implementers are interested (and none opposed):
Tests are written and can be reviewed and commented upon at:
Implementation bugs are filed:
(See WHATWG Working Mode: Changes for more details.)
See: #6637
/browsers.html ( diff )
/origin.html ( diff )
/workers.html ( diff )