Remove the check of the whitelist entries in ClientPhishingResponse.

chrome/common/safe_browsing/csd.proto

 // Copyright (c) 2011 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 //
 // Client side phishing and malware detection request and response
 // protocol buffers.  Those protocol messages should be kept in sync
 // with the server implementation.
 //
 // If you want to change this protocol definition or you have questions
 // regarding its format please contact chrome-anti-phishing@googlegroups.com.
 
 syntax = "proto2";
 
 option optimize_for = LITE_RUNTIME;
 
 package safe_browsing;
 
 message ClientPhishingRequest {
   // URL that the client visited.  The CGI parameters are stripped by the
   // client.  This field is ONLY set for UMA-enabled users.
   optional string url = 1;
 
   // A 5-byte SHA-256 hash prefix of the URL.  Before hashing the URL is
   // canonicalized, converted to a suffix-prefix expression and broadened
   // (www prefix is removed and everything past the last '/' is stripped).
-  // Unlike "url", this is sent for all users.
-  optional bytes hash_prefix = 10;
+  //
+  // Marked OBSOLETE because the URL is sent for all users, making the hash
+  // prefix unnecessary.
+  optional bytes OBSOLETE_hash_prefix = 10;
 
   // Score that was computed on the client.  Value is between 0.0 and 1.0.
   // The larger the value the more likely the url is phishing.
   required float client_score = 2;
 
   // Note: we're skipping tag 3 because it was previously used.
 
   // Is true if the features for this URL were classified as phishing.
   // Currently, this will always be true for all client-phishing requests
   // that are sent to the server.
@@ skipping 32 matching lines @@
   required bool phishy = 1;
 
   // A list of SafeBrowsing host-suffix / path-prefix expressions that
   // are whitelisted.  The client must match the current top-level URL
   // against these whitelisted expressions and only apply a positive
   // phishing verdict above if the URL does not match any expression
   // on this whitelist.  The client must not cache these whitelisted
   // expressions.  This whitelist will be empty for the vast majority
   // of the responses but might contain up to 100 entries in emergency
   // situations.
-  repeated string whitelist_expression = 2;
+  //
+  // Marked OBSOLETE because the URL is sent for all users, so the server
+  // can do whitelist matching.
+  repeated string OBSOLETE_whitelist_expression = 2;
 }
 
 message ClientDownloadRequest {
   // The final URL of the download (after all redirects).
   required string url = 1;
 
   // This message contains various binary digests of the download payload.
   message Digests {
     optional bytes sha256 = 1;
     optional bytes sha1 = 2;
@@ skipping 66 matching lines @@
 message ClientDownloadResponse {
   enum Verdict {
     // Download is considered safe.
     SAFE = 0;
     // Download is considered dangerous.  Chrome should show a warning to the
     // user.
     DANGEROUS = 1;
   }
   required Verdict verdict = 1;
 }