NEW 161654
Fetch API fails to send Origin header on Same Origin GET requests 
https://bugs.webkit.org/show_bug.cgi?id=161654
Summary Fetch API fails to send Origin header on Same Origin GET requests
Mohammed Khatib
Reported 2016-09-06 16:20:20 PDT
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
Attachments
Add attachment proposed patch, testcase, etc.
youenn fablet
Comment 1 2016-09-06 22:43:04 PDT
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
Rob Buis
Comment 2 2019-06-08 01:49:05 PDT
It seems this is fixed; the relevant subtests in api/basic/request-headers.any.js pass and the chromium bug was marked as WontFix.
Note You need to log in before you can comment on or make changes to this bug.