Use API key for SOCS cookie fetching in ChromeOS Compliance API After recently enabling the ChromeOS Compliance API in Chrome project, SocsCookieFetcher would use the Google API key to fetch SOCS cookie. Bug: b/312542928, b/322338027 Change-Id: I4c0cf07c71d25c5cbf9fce9a9f811e14855de4a7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5250567 Auto-Submit: Mohammed Abdon <mohammedabdon@chromium.org> Commit-Queue: Mohammed Abdon <mohammedabdon@chromium.org> Commit-Queue: Maksim Ivanov <emaxx@chromium.org> Reviewed-by: Maksim Ivanov <emaxx@chromium.org> Cr-Commit-Position: refs/heads/main@{#1254557}
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.