Checking this whitelist shouldn't send full-hash checks if the full 32B hash is in the DB, but should send one if there's a hash-prefix match.
The existing CSD phishing check is synchronous since it expects 32 byte hashes. We'll probably need to create a new CheckCsdWhitelistUrl() interface to replace MatchCsdWhitelistUrl(), and change all the existing calls to handle asynchronicity.
This will be just for Pver4, but we'll need to not break Pver3.
Comment 1 by jialiul@chromium.org
, May 5 2017