Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(2019)

Unified Diff: content/common/ssl_status_serialization.cc

Issue 2241213002: Distinguish between SCT invalidity reasons in UMA (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master
Patch Set: Changing _MAX to be the last value Created 4 years, 4 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: content/common/ssl_status_serialization.cc
diff --git a/content/common/ssl_status_serialization.cc b/content/common/ssl_status_serialization.cc
index a105e7ea450fcd953edec497eeb1a87b32eb00c7..5622c187cd436f99164629e4091c5b9957df7c2f 100644
--- a/content/common/ssl_status_serialization.cc
+++ b/content/common/ssl_status_serialization.cc
@@ -31,9 +31,9 @@ bool CheckSecurityStyle(int security_style) {
bool CheckSCTStatus(uint32_t sct_status) {
switch (sct_status) {
case net::ct::SCT_STATUS_LOG_UNKNOWN:
- case net::ct::SCT_STATUS_INVALID:
+ case net::ct::SCT_STATUS_INVALID_SIGNATURE:
case net::ct::SCT_STATUS_OK:
- case net::ct::SCT_STATUS_MAX:
+ case net::ct::SCT_STATUS_INVALID_TIMESTAMP:
return true;
case net::ct::SCT_STATUS_NONE:
// SCT_STATUS_NONE should never happen, so it isn't valid to
« no previous file with comments | « chrome/browser/ui/website_settings/website_settings_unittest.cc ('k') | content/common/ssl_status_serialization_unittest.cc » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698