Set referrer string and referrer policy separately for module script fetching
There is no observable result of this change. Before this CL, ModuleScriptFetchRequest stored a blink::Referrer and a blink::ScriptFetchOptions. This effectively stored two blink::ReferrerPolicy members under ModuleScriptFetchRequest. We also generated ModuleScriptFetchRequest's Referrer in two different places in ModuleTreeLinker. Finally ModuleScriptFetchRequest's Referrer member was used in ModuleScriptLoader::FetchInternal to set ResourceRequest's referrer header. After this CL, we store only a referrer string in ModuleScriptFetchRequest, as the spec indicates, and do not generate a blink::Referrer in ModuleTreeLinker. Then in ModuleScriptLoader::FetchInternal, we generate and set ResourceRequest's final referrer. This also leaves a TODO, to stop storing ResourceRequest's referrer as a header value. R=kinuko@chromium.org, kouhei@chromium.org, nhiroki@chromium.org, yhirano@chromium.org Bug: 863769 Change-Id: Id22467f5c93e59b33ca01571addeceb1a505a1af Reviewed-on: https://chromium-review.googlesource.com/1157237 Commit-Queue: Dominic Farolino <domfarolino@gmail.com> Reviewed-by:Kouhei Ueno <kouhei@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Reviewed-by:
Yutaka Hirano <yhirano@chromium.org> Reviewed-by:
Hiroki Nakagawa <nhiroki@chromium.org> Cr-Commit-Position: refs/heads/master@{#580804}
Showing
Please register or sign in to comment