161654 2016-09-06 16:20:20 -0700 Fetch API fails to send Origin header on Same Origin GET requests 2019-06-08 01:49:05 -0700 1 1 1 Unclassified WebKit WebKit2 WebKit Nightly Build Unspecified Unspecified NEW P2 Normal --- 151937 1 mkhatib727 webkit-unassigned rbuis youennf oldest_to_newest 1226918 0 mkhatib727 2016-09-06 16:20:20 -0700 Safari Dev Preview seems to successfully set Origin header on these cases: * Cross Origin GET * Same Origin POST * Cross Origin POST But fails to do the same with Same Origin GET. Firefox already successfully implements this and Chrome are working on fixing the same issue in their Fetch implementation. https://codereview.chromium.org/2290193003/ https://bugs.chromium.org/p/chromium/issues/detail?id=641620#c2 1227053 1 youennf 2016-09-06 22:43:04 -0700 Thanks for filing this bug. It seems there is consensus to add the Origin header in cors mode, which would cover XHR. It is not very clear what happens in no-cors mode, see https://github.com/whatwg/fetch/issues/225 1543070 2 rbuis 2019-06-08 01:49:05 -0700 It seems this is fixed; the relevant subtests in api/basic/request-headers.any.js pass and the chromium bug was marked as WontFix.