Worker: Set ResourceRequest::upgrade_if_insecure_ for PlzDedicatedWorker and PlzSharedWorker
Before this CL, ResourceRequest for browser-initiated worker script loading (PlzDedicatedWorker and PlzSharedWorker) always doesn't set the |upgrade_if_insecure_| flag, and upgrade-insecure-requests handing completely doesn't work. To fix it, this CL plumbs the flag from outside FetchClientSettingsObject in a renderer process to the request created in the browser process. upgrade-insecure-requests handling works only when the browser-initiated request is redirected from a secure context to an insecure context. For non-redirect case where the request is directly sent to an insecure context from a secure context, upgrade-insecure-requests handling doesn't work because of https://crbug.com/917532 Note that this removes expectation files for virtual/omt-worker-fetch, but some tests are still suppressed by another expectation files for non-virtual. Bug: 906991, 917532, 987491 Change-Id: I690db42609133390fc6dc4aae150e0d94eab3199 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1715899 Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org> Reviewed-by:Hiroshige Hayashizaki <hiroshige@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Cr-Commit-Position: refs/heads/master@{#682634}
Showing
Please register or sign in to comment