Enable verdict cache on safe browsing real time url check.
In this CL, cache_manager is introduced to safe_browsing_url_check via chrome_content_browser_client. It must be not null when real time url check is enabled and the profile is not deleted. Cache is checked and stored on UI thread. url_checker doesn't own cache_manager, so it uses a weak pointer to access it. Weak pointers can only be accessed from the same thread it is created. If cache_manager is able to get a valid matching verdict from the url, regardless of whether the verdict type is safe or dangerous, it will skip sending pings and use that verdict type as the check result. More information can be found in go/chrome-protego-cache. Bug: 1030989 Change-Id: I1195c4777a10de5356078746dc07119f1b0e04c4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1963409 Commit-Queue: Xinghui Lu <xinghuilu@chromium.org> Reviewed-by:Varun Khaneja <vakh@chromium.org> Reviewed-by:
Tim Volodine <timvolodine@chromium.org> Reviewed-by:
Nate Fischer <ntfschr@chromium.org> Reviewed-by:
Bo <boliu@chromium.org> Reviewed-by:
Daniel Rubery <drubery@chromium.org> Cr-Commit-Position: refs/heads/master@{#726084}
Showing
Please register or sign in to comment