fetch: Use a derived origin for file- and opaque-initiated requests
Currently, fetch's request_conversion.cc swaps out the initiators from files and opaque origins, replacing the initiator with a new opaque origin. Switching this to derive an opaque origin will preserve precursor information so that subsequent decisions can be based on, for instance, whether a request came from a file (or whether a request came from an opaque frame with an HTTPS precursor). Bug: 794098 Change-Id: I4f3d6d85e60afd9dda283a54501459705d52d958 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2242635Reviewed-by:Yutaka Hirano <yhirano@chromium.org> Reviewed-by:
Charlie Harrison <csharrison@chromium.org> Reviewed-by:
Łukasz Anforowicz <lukasza@chromium.org> Commit-Queue: David Van Cleve <davidvc@chromium.org> Cr-Commit-Position: refs/heads/master@{#784257}
Showing
Please register or sign in to comment