Skip to content

Add credentialless value to COEP (HTML spec) - #6638

Merged
annevk merged 4 commits into
whatwg:mainfrom
ArthurSonzogni:cors-or-credentialless
Nov 2, 2021
Merged

annevk merged 4 commits into
whatwg:mainfrom
ArthurSonzogni:cors-or-credentialless

Conversation

@ArthurSonzogni

@ArthurSonzogni ArthurSonzogni commented Apr 30, 2021 •

Copy link
Copy Markdown
Member

Originally described in: https://github.com/mikewest/credentiallessness

credentialless and require-corp are similar. One or the other is a requirements for the window.crossOriginIsolated capability.
They differ mostly in the fetch specification. require-corp requires a CORP header for cross-origin no-cors responses. credentialless doesn't, but omits credentials (Cookies, clients certificates, etc...) in the request.

  • HTML (Add credentialless value to COEP (HTML spec) #6638)

    • Define how to parse the credentialless value.
    • From the HTML spec point of view, credentialless and require-corp are equivalent. They have been grouped into compatible with cross-origin isolation and the HTML spec rewritten to use this concept.
  • Fetch: (Specify the behavior of COEP: credentialless, fetch#1229)

    • Define Cross-Origin-Embedder-Policy allows credentials algorithm. It omit credentials for no-cors, cross-origin, COEP:credentialless requests.
    • Define response's request-include-credentials flag.
    • In the Cross-Origin-Resource-Policy check, if embedderPolicy is credentialless, require CORP for navigational responses, and opaque responses with request-include-credentials.

See: #6637


(See WHATWG Working Mode: Changes for more details.)


See: #6637


/browsers.html ( diff )
/origin.html ( diff )
/workers.html ( diff )

Loading
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

addition/proposal New features or enhancements topic: cross-origin-embedder-policy Issues and ideas around the new "require CORP for subresource requests and frames and etc" proposal

Development

Successfully merging this pull request may close these issues.

5 participants