Making CSD ReportType enum consistent.

components/safe_browsing/csd.proto

 // Copyright (c) 2012 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.
 //
 // This proto file includes:
 // (1) Client side phishing and malware detection request and response
 //   protocol buffers.  Those protocol messages should be kept in sync
 //   with the server implementation.
 //
 // (2) Safe Browsing reporting protocol buffers.
@@ skipping 885 matching lines @@
   // Note: A lot of the "optional" fields would make sense to be
   // "required" instead.  However, having them as optional allows the
   // clients to send "stripped down" versions of the message in the
   // future, if we want to.
 
   enum ReportType {
     UNKNOWN = 0;
     URL_PHISHING = 1;
     URL_MALWARE = 2;
     URL_UNWANTED = 3;
-    CLIENT_SIDE_PHISHING_URL = 4;
-    CLIENT_SIDE_MALWARE_URL = 5;
+    URL_CLIENT_SIDE_PHISHING = 4;
+    URL_CLIENT_SIDE_MALWARE = 5;
     DANGEROUS_DOWNLOAD_RECOVERY = 6;
     DANGEROUS_DOWNLOAD_WARNING = 7;
     DANGEROUS_DOWNLOAD_BY_API = 10;
-    PASSWORD_PROTECTION_PHISHING_URL = 12;
+    URL_PASSWORD_PROTECTION_PHISHING = 12;
   }
 
   message HTTPHeader {
     required bytes name = 1;
     optional bytes value = 2;
   }
 
   message HTTPRequest {
     message FirstLine {
       optional bytes verb = 1;
@@ skipping 120 matching lines @@
 // There is no response (an empty body) to this request.
 message NotificationImageReportRequest {
   optional string notification_origin = 1;  // Src-origin of the notification.
   optional ImageData image = 2;             // The bitmap of the image.
 
   // Note that the image URL is deliberately omitted as it would be untrusted,
   // since the notification image fetch may be intercepted by a Service Worker
   // (even if the image URL is cross-origin). Otherwise a website could mislead
   // Safe Browsing into associating phishing image bitmaps with safe image URLs.
 }