0
Files
src/content/browser
Titouan Rigoudy 40a9b51f27 [CORS-RFC1918] Partially fix secure context computation.
This change has the computation take into account the
is_web_secure_context bit as set on the parent document, if any. It is
not immediately clear what to do when the parent document has not
committed a navigation yet. I suspect this ties in to crbug.com/1129326,
in which we might want to look at the *current* frame's client security
state instead, and inherit a value at frame creation time from the
parent.

Also stop computing the client security state for navigation requests
served by the back-forward cache.

Bug: chromium:1126856
Change-Id: I72a3ffddf53eaea04f579c87705eff68508474ec
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2414249
Commit-Queue: Titouan Rigoudy <titouan@chromium.org>
Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org>
Auto-Submit: Titouan Rigoudy <titouan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#808375}
2020-09-18 16:18:09 +00:00
..
2020-08-25 15:23:52 +00:00
2020-09-17 17:33:26 +00:00
2020-06-23 21:54:41 +00:00