Frame Ancestor Headers would expose information about the relationship between a request's ancestor frames and that request's target by adding two new HTTP request headers, `Sec-Fetch-Frame-Top` and `Sec-Fetch-Frame-Ancestors`. This should support developers' understanding of the circumstances in which they may have access to unpartitioned cookies, and the ways in which their resources may be partitioned.
Currently, there is no signal on the web platform that comprehensively indicates the relationship between a request's destination and its ancestor frames. This information is important for sites to understand how cookies may be partitioned on a request and why a request may be autogranted storage access permissions. This feature offers two new headers as signals, `Sec-Fetch-Frame-Top` and `Sec-Fetch-Frame-Ancestors`, whose values will indicate whether a request's destination is `same-origin`, `same-site`, or `cross-site` to its top frame and all of its ancestor frames respectively.
None
While we have not filed formal browser positions yet, a constructive discussion with both Mozilla and Apple is happening at https://github.com/w3c/webappsec-fetch-metadata/pull/89.
None
None
No milestones specified