Set |request_initiator| to the website (fixing XHR as well).
This is a follow-up to r694827 which intended to ensure that |request_initiator| is always set to the website (and not, for example, to the content script's origin), but missed fixing this for XHR API. Note that some follow-ups for r694827 (e.g. r700486 and r704100) have already landed in M79 - these follow-ups assume that |request_initiator| is set to the website origin everywhere. This CL fixes this assumption for XHR. We should consider merging this CL to M79 (otherwise CORB and CORS might incorrectly start to block same-origin XHRs). This CL is also a prerequisite for starting to enforce request_initiator_site_lock in a follow-up CL at https://crrev.com/c/1875273 Bug: 1017448 Change-Id: I8512daf9364aaa10d76c81ef9bcc18f072a2337d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1876981 Auto-Submit: Łukasz Anforowicz <lukasza@chromium.org> Reviewed-by:Karan Bhatia <karandeepb@chromium.org> Reviewed-by:
Yutaka Hirano <yhirano@chromium.org> Commit-Queue: Łukasz Anforowicz <lukasza@chromium.org> Cr-Commit-Position: refs/heads/master@{#710554}
Showing
This diff is collapsed.
Please register or sign in to comment