You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Based on conversations in [1] and [2], `Sec-Fetch-Dest` seems
valuable enough to ship and support. This patch drops the issue
asking that question, and closes#16.
[1]: #16
[2]: whatwg/fetch#948
<p>The following sections define several <dfnclass="dfn-paneled" data-dfn-type="dfn" data-exportid="fetch-metadata-headers">fetch metadata headers</dfn>, each of which
1571
1571
exposes an interesting <adata-link-type="dfn" href="https://fetch.spec.whatwg.org/#concept-request" id="ref-for-concept-request">request</a> attribute to a server.</p>
<pclass="issue" id="issue-d1aaf268"><aclass="self-link" href="#issue-d1aaf268"></a> There are some concerns about the value this header would
1574
-
provide, particularly in the face of a Service Worker’s ability to use cached responses in
1575
-
unexpected ways. It might be worth punting it to a future iteration. <ahref="https://github.com/mikewest/sec-metadata/issues/16"><https://github.com/mikewest/sec-metadata/issues/16></a></p>
1576
1573
<p>The <dfnclass="dfn-paneled" data-dfn-type="http-header" data-exportid="http-headerdef-sec-fetch-dest"><code>Sec-Fetch-Dest</code></dfn> HTTP request header exposes a <adata-link-type="dfn" href="https://fetch.spec.whatwg.org/#concept-request" id="ref-for-concept-request①">request</a>'s <adata-link-type="dfn" href="https://fetch.spec.whatwg.org/#concept-request-destination" id="ref-for-concept-request-destination">destination</a> to a server. It is a <adata-link-type="dfn" href="https://tools.ietf.org/html/draft-ietf-httpbis-header-structure#" id="termref-for-">Structured Header</a> whose value MUST be a <adata-link-type="dfn" href="https://tools.ietf.org/html/draft-ietf-httpbis-header-structure#section-3.7" id="ref-for-section-3.7">token</a>. <adata-link-type="biblio" href="#biblio-i-dietf-httpbis-header-structure">[I-D.ietf-httpbis-header-structure]</a> Its ABNF is:</p>
<p><var>r</var>’s <adata-link-type="dfn" href="https://fetch.spec.whatwg.org/#concept-request-origin" id="ref-for-concept-request-origin②">origin</a>'s <adata-link-type="dfn" href="https://html.spec.whatwg.org/multipage/origin.html#concept-origin-scheme" id="ref-for-concept-origin-scheme">scheme</a> is not the same as <var>url</var>’s <adata-link-type="dfn" href="https://url.spec.whatwg.org/#concept-url-scheme" id="ref-for-concept-url-scheme">scheme</a></p>
1674
1671
<lidata-md>
1675
-
<p><var>r</var>’s <adata-link-type="dfn" href="https://fetch.spec.whatwg.org/#concept-request-origin" id="ref-for-concept-request-origin③">origin</a>'s <adata-link-type="dfn" href="https://html.spec.whatwg.org/multipage/origin.html#concept-origin-host" id="ref-for-concept-origin-host">host</a> is not <adata-link-type="dfn" href="https://url.spec.whatwg.org/#host-same-site" id="ref-for-host-same-site">same site</a> with <var>url</var>’s <adata-link-type="dfn" href="https://url.spec.whatwg.org/#concept-url-host" id="ref-for-concept-url-host">host</a></p>
1672
+
<p><var>r</var>’s <adata-link-type="dfn" href="https://fetch.spec.whatwg.org/#concept-request-origin" id="ref-for-concept-request-origin③">origin</a>'s <adata-link-type="dfn" href="https://html.spec.whatwg.org/multipage/origin.html#concept-origin-host" id="ref-for-concept-origin-host">host</a> is not <adata-link-type="dfn" href="https://html.spec.whatwg.org/multipage/origin.html#same-site" id="ref-for-same-site">same site</a> with <var>url</var>’s <adata-link-type="dfn" href="https://url.spec.whatwg.org/#concept-url-host" id="ref-for-concept-url-host">host</a></p>
1676
1673
</ul>
1677
1674
<lidata-md>
1678
1675
<p>Set <var>header</var>’s value to <code>same-site</code>.</p>
<divclass="issue"> There are some concerns about the value this header would
2258
-
provide, particularly in the face of a Service Worker’s ability to use cached responses in
2259
-
unexpected ways. It might be worth punting it to a future iteration. <ahref="https://github.com/mikewest/sec-metadata/issues/16"><https://github.com/mikewest/sec-metadata/issues/16></a><ahref="#issue-d1aaf268"> ↵ </a></div>
2260
2254
<divclass="issue"> This flag is defined here, in <ahref="#fetch-integration">§ 3 Integration with Fetch and HTML</a>. Ideally,
2261
2255
we can move it to Fetch rather than monkey-patching. <ahref="https://github.com/whatwg/fetch/issues/885"><https://github.com/whatwg/fetch/issues/885></a><ahref="#issue-43037b44"> ↵ </a></div>
0 commit comments