commit | 6a54f7abc42d7b04ec913d90453838a9b82d3d9c | [log] [tgz] |
---|---|---|
author | Andreea Costinas <acostinas@google.com> | Wed Nov 23 11:23:18 2022 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Nov 23 11:23:18 2022 |
tree | 32532914340496c5cde8848ce3a0410d5ae77d48 | |
parent | a604c1b183e45e65e61b04a3e74447d1d831b332 [diff] |
Add policies to control the DNS over HTTPS identifiers feature This allows to set the policies DnsOverHttpsTemplatesWithIdentifiers and DnsOverHttpsSalt to allow including variables in the template. Those variables will then be evaluated when generating the final URI to be passed to the DNS over HTTPS server. The server can use the content of the variables for making logging or routing decisions. The feature is only supported on ChromeOS. For other OSs the original policy DnsOverHttpsTemplates will be used (if set) which does not allow including variables. The cross platform policy DnsOverHttpsTemplates was not extended with identifiers to preserve existing behavior and because the client request asks for machine identifiers which are not available on other platforms. This CL only adds the policies, for the implementation see the followup CL:4013345. This CL was originally reviewed as CL:3913063. Bug: b/230468360 Change-Id: I41b976f35f4d9cccca3c8b05b4e2765c55d4570e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3990794 Reviewed-by: Eric Orth <ericorth@chromium.org> Reviewed-by: Roland Bock <rbock@google.com> Reviewed-by: Pavol Marko <pmarko@chromium.org> Reviewed-by: Adam Rice <ricea@chromium.org> Commit-Queue: Andreea Costinas <acostinas@google.com> Reviewed-by: Kyle Horimoto <khorimoto@chromium.org> Cr-Commit-Position: refs/heads/main@{#1075090}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.