Bug 246508 - Implement Fetch Metadata Request Headers (aka Sec-Fetch-*)
Summary: Implement Fetch Metadata Request Headers (aka Sec-Fetch-*)
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: DOM (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Patrick Griffis
URL: https://w3c.github.io/webappsec-fetch...
Keywords: InRadar
Depends on: 204744 237550 238265 253265
Blocks:
  Show dependency tree / graph
 
Reported: 2022-10-14 00:58 PDT by Anne van Kesteren
Modified: 2023-03-02 13:58 PST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Anne van Kesteren 2022-10-14 00:58:42 PDT 
This is a tracking bug for the various dedicated Fetch Metadata bugs. Seems all headers apart from Sec-Fetch-Site and Sec-Fetch-User are covered thus far, but Sec-Fetch-Site has a patch.
Comment 1 Radar WebKit Bug Importer 2022-10-14 00:58:54 PDT 
<rdar://problem/101162929>
Comment 2 Patrick Griffis 2022-10-21 08:55:06 PDT 
I don't plan on working on Sec-Fetch-User, at least for now. Discussing it with some people from Google they said that User wasn't very reliable nor the most important of them.

It should be doable in WebKit but it seemed less straightforward that Chromium which has more direct access to the browser UI layers to track user actions.

I'd like to see the current work that is done at least move to be enabled as an experimental feature.
Comment 3 Patrick Griffis 2022-11-07 09:51:49 PST 
Pull request: https://github.com/WebKit/WebKit/pull/6211
Comment 4 EWS 2022-11-08 11:44:53 PST 
Committed 256456@main (cb60df93ab8c): <https://commits.webkit.org/256456@main>

Reviewed commits have been landed. Closing PR #6211 and removing active labels.
Comment 5 Anne van Kesteren 2022-11-09 02:14:47 PST 
Patrick, this wasn't meant to be the "enable by default" bug. Now we have nothing open to track the remaining WebSocket-related issue as well as Sec-Fetch-User. Could you file a new tracking bug perhaps as I guess we cannot reopen this one now it's associated with that PR?
Comment 6 Patrick Griffis 2022-11-09 13:52:50 PST 
Sorry about that. I opened https://bugs.webkit.org/show_bug.cgi?id=247696