CloudBinaryUploadService (CBUS) should recheck authorization if the previous one fails. Note: This approach should not add too much traffic to the reporting server because: 1. With the license check on DM Server side, BCE policies will not be pushed to browsers if the admin doesn't have valid BCE license. Therefore, Chrome won't send data to CBUS for processing if the DM Server check is not passed. 2. The authorization request that CBUS uses is an empty request with dm_token, connector type, and other metadata copied over from the actual scanning request. If the upload result is not successful, CBUS won't upload the actual content for analysis. Bug: b/315152603, b/301996227 Change-Id: I83b5086471166eeaabc2466339e37d92dc90ff80 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5095594 Reviewed-by: Daniel Rubery <drubery@chromium.org> Reviewed-by: Roger Tawa <rogerta@chromium.org> Code-Coverage: findit-for-me@appspot.gserviceaccount.com <findit-for-me@appspot.gserviceaccount.com> Commit-Queue: Nancy Xiao <nancylanxiao@google.com> Reviewed-by: Dominique Fauteux-Chapleau <domfc@chromium.org> Cr-Commit-Position: refs/heads/main@{#1235992}
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.