Chrome Participated Tamper Detect

tools/metrics/histograms/histograms.xml

Index: tools/metrics/histograms/histograms.xml
diff --git a/tools/metrics/histograms/histograms.xml b/tools/metrics/histograms/histograms.xml
index 7f30d67426da00b81eebe611bf3518c8026fb518..08fd5609570a60e4cbcb00deb4fb277a1aca42a3 100644
--- a/tools/metrics/histograms/histograms.xml
+++ b/tools/metrics/histograms/histograms.xml
@@ -3158,6 +3158,493 @@ Therefore, the affected-histogram name has to have at least one dot in it.
   </summary>
 </histogram>
 
+<histogram name="DataReductionProxy.HTTPHeaderTamperDetection">
+  <owner>xingx@chromium.org</owner>
+  <owner>bolian@chromium.org</owner>
+  <owner>bengr@chromium.org</owner>
+  <summary>
+    For each carrier, the total number of HTTP responses that have been checked
+    for tampering. This assumes the data reduction proxy injected fingerprints
+    are not tampered. Only the data reduction proxy responses with 200 OK

[bengr, 2014/07/28 21:56:53]

are not tampered --> have not been tampered with.

Here and below.

[xingx1, 2014/07/30 03:44:22]

Done.

+    response code are checked.
+  </summary>
+</histogram>
+
+<histogram name="DataReductionProxy.HTTPHeaderTamperDetection_Total">
+  <owner>xingx@chromium.org</owner>
+  <owner>bolian@chromium.org</owner>
+  <owner>bengr@chromium.org</owner>
+  <summary>
+    The total number of HTTP responses that have been checked for tampering.
+    This assumes the data reduction proxy injected fingerprints are not
+    tampered. Only the data reduction proxy responses with 200 OK response code
+    are checked.
+  </summary>
+</histogram>
+
+<histogram name="DataReductionProxy.HTTPHeaderTampered_ChromeProxy">
+  <owner>xingx@chromium.org</owner>
+  <owner>bolian@chromium.org</owner>
+  <owner>bengr@chromium.org</owner>
+  <summary>
+    For each carrier, the total number of HTTP responses whose Chrome-Proxy
+    header has been tampered with. This assumes the data reduction proxy
+    injected fingerprints are not tampered. Only the data reduction proxy
+    responses with 200 OK response code are checked.
+  </summary>
+</histogram>
+
+<histogram name="DataReductionProxy.HTTPHeaderTampered_ChromeProxy_Total">
+  <owner>xingx@chromium.org</owner>
+  <owner>bolian@chromium.org</owner>
+  <owner>bengr@chromium.org</owner>
+  <summary>
+    The total number of HTTP responses whose Chrome-Proxy header has been
+    tampered with. This assumes the data reduction proxy injected fingerprints
+    are not tampered. Only the data reduction proxy responses with 200 OK
+    response code are checked.
+  </summary>
+</histogram>
+
+<histogram name="DataReductionProxy.HTTPHeaderTampered_ContentLength">
+  <owner>xingx@chromium.org</owner>
+  <owner>bolian@chromium.org</owner>
+  <owner>bengr@chromium.org</owner>
+  <summary>
+    For each carrier, the total number of HTTP responses whose Content-Length
+    header has been tampered with. This assumes the data reduction proxy
+    injected fingerprints are not tampered. Only the data reduction proxy
+    responses with 200 OK response code are checked.
+  </summary>
+</histogram>
+
+<histogram name="DataReductionProxy.HTTPHeaderTampered_ContentLength_CSS">
+  <owner>xingx@chromium.org</owner>
+  <owner>bolian@chromium.org</owner>
+  <owner>bengr@chromium.org</owner>
+  <summary>
+    For each carrier, the total number of HTTP responses of CSS object whose
+    Content-Length header has been tampered with. This assumes the data
+    reduction proxy injected fingerprints are not tampered. Only the data
+    reduction proxy responses with 200 OK response code are checked.
+  </summary>
+</histogram>
+
+<histogram name="DataReductionProxy.HTTPHeaderTampered_ContentLength_CSS_Total">
+  <owner>xingx@chromium.org</owner>
+  <owner>bolian@chromium.org</owner>
+  <owner>bengr@chromium.org</owner>
+  <summary>
+    The total number of HTTP responses of CSS object whose Content-Length header
+    has been tampered with. This assumes the data reduction proxy injected
+    fingerprints are not tampered. Only the data reduction proxy responses with
+    200 OK response code are checked.
+  </summary>
+</histogram>
+
+<histogram name="DataReductionProxy.HTTPHeaderTampered_ContentLength_Image">
+  <owner>xingx@chromium.org</owner>
+  <owner>bolian@chromium.org</owner>
+  <owner>bengr@chromium.org</owner>
+  <summary>
+    For each carrier, the total number of HTTP responses of image object whose
+    Content-Length header has been tampered with. This assumes the data
+    reduction proxy injected fingerprints are not tampered. Only the data
+    reduction proxy responses with 200 OK response code are checked.
+  </summary>
+</histogram>
+
+<histogram
+    name="DataReductionProxy.HTTPHeaderTampered_ContentLength_Image_Total">
+  <owner>xingx@chromium.org</owner>
+  <owner>bolian@chromium.org</owner>
+  <owner>bengr@chromium.org</owner>
+  <summary>
+    The total number of HTTP responses of image object whose Content-Length
+    header has been tampered with. This assumes the data reduction proxy
+    injected fingerprints are not tampered. Only the data reduction proxy
+    responses with 200 OK response code are checked.
+  </summary>
+</histogram>
+
+<histogram name="DataReductionProxy.HTTPHeaderTampered_ContentLength_JS">
+  <owner>xingx@chromium.org</owner>
+  <owner>bolian@chromium.org</owner>
+  <owner>bengr@chromium.org</owner>
+  <summary>
+    For each carrier, the total number of HTTP responses of JavaScript object
+    whose Content-Length header has been tampered with. This assumes the data
+    reduction proxy injected fingerprints are not tampered. Only the data
+    reduction proxy responses with 200 OK response code are checked.
+  </summary>
+</histogram>
+
+<histogram name="DataReductionProxy.HTTPHeaderTampered_ContentLength_JS_Total">
+  <owner>xingx@chromium.org</owner>
+  <owner>bolian@chromium.org</owner>
+  <owner>bengr@chromium.org</owner>
+  <summary>
+    The total number of HTTP responses of JavaScript object whose Content-Length
+    header has been tampered with. This assumes the data reduction proxy
+    injected fingerprints are not tampered. Only the data reduction proxy
+    responses with 200 OK response code are checked.
+  </summary>
+</histogram>
+
+<histogram name="DataReductionProxy.HTTPHeaderTampered_ContentLength_Other">
+  <owner>xingx@chromium.org</owner>
+  <owner>bolian@chromium.org</owner>
+  <owner>bengr@chromium.org</owner>
+  <summary>
+    For each carrier, the total number of HTTP responses of all other objects
+    whose Content-Length header has been tampered with. This assumes the data
+    reduction proxy injected fingerprints are not tampered. Only the data
+    reduction proxy responses with 200 OK response code are checked.
+  </summary>
+</histogram>
+
+<histogram
+    name="DataReductionProxy.HTTPHeaderTampered_ContentLength_Other_Total">
+  <owner>xingx@chromium.org</owner>
+  <owner>bolian@chromium.org</owner>
+  <owner>bengr@chromium.org</owner>
+  <summary>
+    The total number of HTTP responses of all other objects whose Content-Length
+    header has been tampered with. This assumes the data reduction proxy
+    injected fingerprints are not tampered. Only the data reduction proxy
+    responses with 200 OK response code are checked.
+  </summary>
+</histogram>
+
+<histogram name="DataReductionProxy.HTTPHeaderTampered_ContentLength_Total">
+  <owner>xingx@chromium.org</owner>
+  <owner>bolian@chromium.org</owner>
+  <owner>bengr@chromium.org</owner>
+  <summary>
+    The total number of HTTP responses whose Chrome-Proxy header has been
+    tampered with. This assumes the data reduction proxy injected fingerprints
+    are not tampered. Only the data reduction proxy responses with 200 OK
+    response code are checked.
+  </summary>
+</histogram>
+
+<histogram name="DataReductionProxy.HTTPHeaderTampered_OtherHeaders">
+  <owner>xingx@chromium.org</owner>
+  <owner>bolian@chromium.org</owner>
+  <owner>bengr@chromium.org</owner>
+  <summary>
+    For each carrier, the total number of HTTP responses whose some other
+    headers have been tampered with. This assumes the data reduction proxy
+    injected fingerprints are not tampered. Only the data reduction proxy
+    responses with 200 OK response code are checked.
+  </summary>
+</histogram>
+
+<histogram name="DataReductionProxy.HTTPHeaderTampered_OtherHeaders_Total">
+  <owner>xingx@chromium.org</owner>
+  <owner>bolian@chromium.org</owner>
+  <owner>bengr@chromium.org</owner>
+  <summary>
+    The total number of HTTP responses whose some other headers have been
+    tampered with. This assumes the data reduction proxy injected fingerprints
+    are not tampered. Only the data reduction proxy responses with 200 OK
+    response code are checked.
+  </summary>
+</histogram>
+
+<histogram name="DataReductionProxy.HTTPHeaderTampered_Via">
+  <owner>xingx@chromium.org</owner>
+  <owner>bolian@chromium.org</owner>
+  <owner>bengr@chromium.org</owner>
+  <summary>
+    For each carrier, the total number of HTTP responses whose Via header shows
+    intermediaries between the Chromium client and the data reduction proxy.
+    This assumes the data reduction proxy injected fingerprints are not
+    tampered. Only the data reduction proxy responses with 200 OK response code
+    are checked.
+  </summary>
+</histogram>
+
+<histogram name="DataReductionProxy.HTTPHeaderTampered_Via_Missing">
+  <owner>xingx@chromium.org</owner>
+  <owner>bolian@chromium.org</owner>
+  <owner>bengr@chromium.org</owner>
+  <summary>
+    For each carrier, the total number of HTTP responses whose data reduction
+    proxy's Via header is missing. This assumes the data reduction proxy
+    injected fingerprints are not tampered. Only the data reduction proxy
+    responses with 200 OK response code are checked.
+  </summary>
+</histogram>
+
+<histogram name="DataReductionProxy.HTTPHeaderTampered_Via_Missing_Total">
+  <owner>xingx@chromium.org</owner>
+  <owner>bolian@chromium.org</owner>
+  <owner>bengr@chromium.org</owner>
+  <summary>
+    The total number of HTTP responses whose data reduction proxy's Via header
+    is missing. This assumes the data reduction proxy injected fingerprints are
+    not tampered. Only the data reduction proxy responses with 200 OK response
+    code are checked.
+  </summary>
+</histogram>
+
+<histogram name="DataReductionProxy.HTTPHeaderTampered_Via_Total">
+  <owner>xingx@chromium.org</owner>
+  <owner>bolian@chromium.org</owner>
+  <owner>bengr@chromium.org</owner>
+  <summary>
+    The total number of HTTP responses whose Via header shows intermediaries
+    between the Chromium client and the data reduction proxy. This assumes the
+    data reduction proxy injected fingerprints are not tampered. Only the data
+    reduction proxy responses with 200 OK response code are checked.
+  </summary>
+</histogram>
+
+<histogram name="DataReductionProxy.HTTPSHeaderTamperDetection">
+  <owner>xingx@chromium.org</owner>
+  <owner>bolian@chromium.org</owner>
+  <owner>bengr@chromium.org</owner>
+  <summary>
+    For each carrier, the total number of HTTPS responses that have been checked
+    for tampering. This assumes the data reduction proxy injected fingerprints
+    are not tampered. Only the data reduction proxy responses with 200 OK
+    response code are checked.
+  </summary>
+</histogram>
+
+<histogram name="DataReductionProxy.HTTPSHeaderTamperDetection_Total">
+  <owner>xingx@chromium.org</owner>
+  <owner>bolian@chromium.org</owner>
+  <owner>bengr@chromium.org</owner>
+  <summary>
+    The total number of HTTPS responses that have been checked for tampering.
+    This assumes the data reduction proxy injected fingerprints are not
+    tampered. Only the data reduction proxy responses with 200 OK response code
+    are checked.
+  </summary>
+</histogram>
+
+<histogram name="DataReductionProxy.HTTPSHeaderTampered_ChromeProxy">
+  <owner>xingx@chromium.org</owner>
+  <owner>bolian@chromium.org</owner>
+  <owner>bengr@chromium.org</owner>
+  <summary>
+    For each carrier, the total number of HTTPS responses whose Chrome-Proxy
+    header has been tampered with. This assumes the data reduction proxy
+    injected fingerprints are not tampered. Only the data reduction proxy
+    responses with 200 OK response code are checked.
+  </summary>
+</histogram>
+
+<histogram name="DataReductionProxy.HTTPSHeaderTampered_ChromeProxy_Total">
+  <owner>xingx@chromium.org</owner>
+  <owner>bolian@chromium.org</owner>
+  <owner>bengr@chromium.org</owner>
+  <summary>
+    The total number of HTTPS responses whose Chrome-Proxy header has been
+    tampered with. This assumes the data reduction proxy injected fingerprints
+    are not tampered. Only the data reduction proxy responses with 200 OK
+    response code are checked.
+  </summary>
+</histogram>
+
+<histogram name="DataReductionProxy.HTTPSHeaderTampered_ContentLength">
+  <owner>xingx@chromium.org</owner>
+  <owner>bolian@chromium.org</owner>
+  <owner>bengr@chromium.org</owner>
+  <summary>
+    For each carrier, the total number of HTTPS responses whose Content-Length
+    header has been tampered with. This assumes the data reduction proxy
+    injected fingerprints are not tampered. Only the data reduction proxy
+    responses with 200 OK response code are checked.
+  </summary>
+</histogram>
+
+<histogram name="DataReductionProxy.HTTPSHeaderTampered_ContentLength_CSS">
+  <owner>xingx@chromium.org</owner>
+  <owner>bolian@chromium.org</owner>
+  <owner>bengr@chromium.org</owner>
+  <summary>
+    For each carrier, the total number of HTTPS responses of CSS object whose
+    Content-Length header has been tampered with. This assumes the data
+    reduction proxy injected fingerprints are not tampered. Only the data
+    reduction proxy responses with 200 OK response code are checked.
+  </summary>
+</histogram>
+
+<histogram
+    name="DataReductionProxy.HTTPSHeaderTampered_ContentLength_CSS_Total">
+  <owner>xingx@chromium.org</owner>
+  <owner>bolian@chromium.org</owner>
+  <owner>bengr@chromium.org</owner>
+  <summary>
+    The total number of HTTPS responses of CSS object whose Content-Length
+    header has been tampered with. This assumes the data reduction proxy
+    injected fingerprints are not tampered. Only the data reduction proxy
+    responses with 200 OK response code are checked.
+  </summary>
+</histogram>
+
+<histogram name="DataReductionProxy.HTTPSHeaderTampered_ContentLength_Image">
+  <owner>xingx@chromium.org</owner>
+  <owner>bolian@chromium.org</owner>
+  <owner>bengr@chromium.org</owner>
+  <summary>
+    For each carrier, the total number of HTTPS responses of image object whose
+    Content-Length header has been tampered with. This assumes the data
+    reduction proxy injected fingerprints are not tampered. Only the data
+    reduction proxy responses with 200 OK response code are checked.
+  </summary>
+</histogram>
+
+<histogram
+    name="DataReductionProxy.HTTPSHeaderTampered_ContentLength_Image_Total">
+  <owner>xingx@chromium.org</owner>
+  <owner>bolian@chromium.org</owner>
+  <owner>bengr@chromium.org</owner>
+  <summary>
+    The total number of HTTPS responses of image object whose Content-Length
+    header has been tampered with. This assumes the data reduction proxy
+    injected fingerprints are not tampered. Only the data reduction proxy
+    responses with 200 OK response code are checked.
+  </summary>
+</histogram>
+
+<histogram name="DataReductionProxy.HTTPSHeaderTampered_ContentLength_JS">
+  <owner>xingx@chromium.org</owner>
+  <owner>bolian@chromium.org</owner>
+  <owner>bengr@chromium.org</owner>
+  <summary>
+    For each carrier, the total number of HTTPS responses of JavaScript object
+    whose Content-Length header has been tampered with. This assumes the data
+    reduction proxy injected fingerprints are not tampered. Only the data
+    reduction proxy responses with 200 OK response code are checked.
+  </summary>
+</histogram>
+
+<histogram name="DataReductionProxy.HTTPSHeaderTampered_ContentLength_JS_Total">
+  <owner>xingx@chromium.org</owner>
+  <owner>bolian@chromium.org</owner>
+  <owner>bengr@chromium.org</owner>
+  <summary>
+    The total number of HTTPS responses of JavaScript object whose
+    Content-Length header has been tampered with. This assumes the data
+    reduction proxy injected fingerprints are not tampered. Only the data
+    reduction proxy responses with 200 OK response code are checked.
+  </summary>
+</histogram>
+
+<histogram name="DataReductionProxy.HTTPSHeaderTampered_ContentLength_Other">
+  <owner>xingx@chromium.org</owner>
+  <owner>bolian@chromium.org</owner>
+  <owner>bengr@chromium.org</owner>
+  <summary>
+    For each carrier, the total number of HTTPS responses of all other objects
+    whose Content-Length header has been tampered with. This assumes the data
+    reduction proxy injected fingerprints are not tampered. Only the data
+    reduction proxy responses with 200 OK response code are checked.
+  </summary>
+</histogram>
+
+<histogram
+    name="DataReductionProxy.HTTPSHeaderTampered_ContentLength_Other_Total">
+  <owner>xingx@chromium.org</owner>
+  <owner>bolian@chromium.org</owner>
+  <owner>bengr@chromium.org</owner>
+  <summary>
+    The total number of HTTPS responses of all other objects whose
+    Content-Length header has been tampered with. This assumes the data
+    reduction proxy injected fingerprints are not tampered. Only the data
+    reduction proxy responses with 200 OK response code are checked.
+  </summary>
+</histogram>
+
+<histogram name="DataReductionProxy.HTTPSHeaderTampered_ContentLength_Total">
+  <owner>xingx@chromium.org</owner>
+  <owner>bolian@chromium.org</owner>
+  <owner>bengr@chromium.org</owner>
+  <summary>
+    The total number of HTTPS responses whose Chrome-Proxy header has been
+    tampered with. This assumes the data reduction proxy injected fingerprints
+    are not tampered. Only the data reduction proxy responses with 200 OK
+    response code are checked.
+  </summary>
+</histogram>
+
+<histogram name="DataReductionProxy.HTTPSHeaderTampered_OtherHeaders">
+  <owner>xingx@chromium.org</owner>
+  <owner>bolian@chromium.org</owner>
+  <owner>bengr@chromium.org</owner>
+  <summary>
+    For each carrier, the total number of HTTPS responses whose some other
+    headers have been tampered with. This assumes the data reduction proxy
+    injected fingerprints are not tampered. Only the data reduction proxy
+    responses with 200 OK response code are checked.
+  </summary>
+</histogram>
+
+<histogram name="DataReductionProxy.HTTPSHeaderTampered_OtherHeaders_Total">
+  <owner>xingx@chromium.org</owner>
+  <owner>bolian@chromium.org</owner>
+  <owner>bengr@chromium.org</owner>
+  <summary>
+    The total number of HTTPS responses whose some other headers have been
+    tampered with. This assumes the data reduction proxy injected fingerprints
+    are not tampered. Only the data reduction proxy responses with 200 OK
+    response code are checked.
+  </summary>
+</histogram>
+
+<histogram name="DataReductionProxy.HTTPSHeaderTampered_Via">
+  <owner>xingx@chromium.org</owner>
+  <owner>bolian@chromium.org</owner>
+  <owner>bengr@chromium.org</owner>
+  <summary>
+    For each carrier, the total number of HTTPS responses whose Via header shows
+    intermediaries between the Chromium client and the data reduction proxy.
+    This assumes the data reduction proxy injected fingerprints are not
+    tampered. Only the data reduction proxy responses with 200 OK response code
+    are checked.
+  </summary>
+</histogram>
+
+<histogram name="DataReductionProxy.HTTPSHeaderTampered_Via_Missing">
+  <owner>xingx@chromium.org</owner>
+  <owner>bolian@chromium.org</owner>
+  <owner>bengr@chromium.org</owner>
+  <summary>
+    For each carrier, the total number of HTTPS responses whose data reduction
+    proxy's Via header is missing. This assumes the data reduction proxy
+    injected fingerprints are not tampered. Only the data reduction proxy
+    responses with 200 OK response code are checked.
+  </summary>
+</histogram>
+
+<histogram name="DataReductionProxy.HTTPSHeaderTampered_Via_Missing_Total">
+  <owner>xingx@chromium.org</owner>
+  <owner>bolian@chromium.org</owner>
+  <owner>bengr@chromium.org</owner>
+  <summary>
+    The total number of HTTPS responses whose data reduction proxy's Via header
+    is missing. This assumes the data reduction proxy injected fingerprints are
+    not tampered. Only the data reduction proxy responses with 200 OK response
+    code are checked.
+  </summary>
+</histogram>
+
+<histogram name="DataReductionProxy.HTTPSHeaderTampered_Via_Total">
+  <owner>xingx@chromium.org</owner>
+  <owner>bolian@chromium.org</owner>
+  <owner>bengr@chromium.org</owner>
+  <summary>
+    The total number of HTTPS responses whose Via header shows intermediaries
+    between the Chromium client and the data reduction proxy. This assumes the
+    data reduction proxy injected fingerprints are not tampered. Only the data
+    reduction proxy responses with 200 OK response code are checked.
+  </summary>
+</histogram>
+
 <histogram name="DataReductionProxy.NetworkChangeEvents"
     enum="DataReductionProxyNetworkChangeEvent">
   <owner>bengr@chromium.org</owner>