UMA now retries over HTTP on upload failures.
The UMA client now retries uploads over an HTTP connection if HTTPS
fails. Logs uploaded over HTTP are encrypted first, along with their
hash and ReportingInfo headers using the encrypted messages component.
Currently this only happens if chrome is started with the
--retry-uma-over-http flag. Tests were also added that validate HTTP
uploads are encrypted and HTTPS ones are not.
In a future CL the UMA.LogUpload.ResponseOrErrorCode histogram will be
split so requests made over HTTP have a separate histogram from those
done over HTTPS.
Bug: 769145
Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: Id0671c49f6bd979343d7e88e04938f567005375e
Reviewed-on: https://chromium-review.googlesource.com/727264
Reviewed-by: Steven Holte <[email protected]>
Reviewed-by: Adrienne Porter Felt <[email protected]>
Reviewed-by: Bo <[email protected]>
Reviewed-by: Olivier Robin <[email protected]>
Commit-Queue: Carlos IL <[email protected]>
Cr-Commit-Position: refs/heads/master@{#514342}diff --git a/components/metrics/test_metrics_service_client.cc b/components/metrics/test_metrics_service_client.cc
index 592af63..348c32b 100644
--- a/components/metrics/test_metrics_service_client.cc
+++ b/components/metrics/test_metrics_service_client.cc
@@ -61,6 +61,7 @@
std::unique_ptr<MetricsLogUploader> TestMetricsServiceClient::CreateUploader(
base::StringPiece server_url,
+ base::StringPiece insecure_server_url,
base::StringPiece mime_type,
MetricsLogUploader::MetricServiceType service_type,
const MetricsLogUploader::UploadCallback& on_upload_complete) {
