Add domain request detection to incident reporting service.

chrome/common/safe_browsing/csd.proto

Index: chrome/common/safe_browsing/csd.proto
diff --git a/chrome/common/safe_browsing/csd.proto b/chrome/common/safe_browsing/csd.proto
index cf487918fdfe4e0d7249bcbfc6a9fc84decbeea4..abd6d3258d4e3e0148750933c83e721fcba4d0f7 100644
--- a/chrome/common/safe_browsing/csd.proto
+++ b/chrome/common/safe_browsing/csd.proto
@@ -371,6 +371,10 @@ message ClientIncidentReport {
       optional string script_digest = 1;
       optional string inclusion_origin = 2;
     }
+    message DomainRequestIncident {

[grt (UTC plus 2), 2015/03/20 20:50:04]

This new type is so similar to the existing one, that I think it makes sense to
generalize the existing one a bit. With the wonder of protobufs, we can change
ScriptRequestIncident to:

  message ResourceIncident {
    enum Type {
      SCRIPT = 0;
      DOMAIN = 1;
    }
    optional string digest = 1;
    optional string origin = 2;
    optional Type type = 3;
  }

and update the various class and method names accordingly.

[grt (UTC plus 2), 2015/03/21 01:30:07]

I just remembered that enums in protobufs must start with an "unknown" value for
the sake of extensibility, so make that:

enum Type {
  UNKNOWN = 0;
  SCRIPT = 1;
  DOMAIN = 2;
}

[romanl, 2015/03/26 22:01:47]

Done.

[romanl, 2015/03/26 22:01:47]

Done.

+      optional string domain_digest = 1;
+      optional string request_origin = 2;
+    }
     optional int64 incident_time_msec = 1;
     optional TrackedPreferenceIncident tracked_preference = 2;
     optional BinaryIntegrityIncident binary_integrity = 3;
@@ -378,6 +382,7 @@ message ClientIncidentReport {
     // Note: skip tag 5 because it was previously used.
     optional VariationsSeedSignatureIncident variations_seed_signature = 6;
     optional ScriptRequestIncident script_request = 7;
+    optional DomainRequestIncident domain_request = 8;
   }
 
   repeated IncidentData incident = 1;