Commit 679b29ef authored by Steven Valdez's avatar Steven Valdez Committed by Commit Bot

Fix up histograms for TLS13 Downgrade.

Bug: boringssl:226
Change-Id: I9541ae612322776a7ccddd8e163ab3025dba1e7a
Reviewed-on: https://chromium-review.googlesource.com/1188849Reviewed-by: default avatarDavid Benjamin <davidben@chromium.org>
Reviewed-by: default avatarIlya Sherman <isherman@chromium.org>
Commit-Queue: Steven Valdez <svaldez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#586260}
parent da886a97
......@@ -57648,8 +57648,10 @@ uploading your change for review.
</summary>
</histogram>
<histogram name="Net.SSLTLS13DowngradeTLS13Experiment" enum="BooleanDowngrade">
<owner>svaldez@chromium.org,davidben@chromium.org</owner>
<histogram name="Net.SSLTLS13DowngradeTLS13Experiment" enum="BooleanDowngrade"
expires_after="2019-03-31">
<owner>svaldez@chromium.org</owner>
<owner>davidben@chromium.org</owner>
<summary>
For each HTTPS connection to the TLS 1.3 experiment server set, whether the
TLS 1.3 anti-downgrade mechanism would have fired. This is only recorded if
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment