As part of the FetchMetadata spec they don't use the normal request modes they have a distinct one. I plan on working on this soon.
<rdar://problem/90106854>
Created attachment 456044 [details] Test case
Attached is a test case for this, however running it Chromium does not attach any metadata to the websocket handshake request, the same as our current behavior. Firefox *does* attach metadata for this so there is an inconsistency there.
Per Fetch they should be included. The handshake goes through the normal fetch algorithm after all and there's no special casing for setting these request headers.
Pull request: https://github.com/WebKit/WebKit/pull/6296
Committed 256527@main (f05061a1e830): <https://commits.webkit.org/256527@main> Reviewed commits have been landed. Closing PR #6296 and removing active labels.