Disable client hints on insecure contexts.
This only affects the client hints that are requested by origins using "Accept-CH" header. Before this change, origins can request client hints using the main frame response. Chrome would then attach the requested client hints on either HTTP or HTTPS subresources. With this change, the client hints would be attached on HTTPS subresources only. This is guarded behind a WebRuntimeFeature which will be enabled after external communication on blink-dev. This is a partial revert of https://chromium-review.googlesource.com/c/chromium/src/+/852863. Bug: 782381 Change-Id: I462178bd6ed3fe08faa2ee67dcba306468ae1ca8 Reviewed-on: https://chromium-review.googlesource.com/887348Reviewed-by:Kinuko Yasuda <kinuko@chromium.org> Reviewed-by:
Ryan Sturm <ryansturm@chromium.org> Commit-Queue: Tarun Bansal <tbansal@chromium.org> Cr-Commit-Position: refs/heads/master@{#532079}
Showing
Please register or sign in to comment