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

Unified Diff: content/common/ssl_status_serialization.cc

Issue 2277653002: Bring back SCT_STATUS_INVALID for cached entries (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master
Patch Set: fix SCT_STATUS_INVALID comment to not refer to disk cache 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 5622c187cd436f99164629e4091c5b9957df7c2f..3785d277eafc0a1cc70ce2a39056563bda47803d 100644
--- a/content/common/ssl_status_serialization.cc
+++ b/content/common/ssl_status_serialization.cc
@@ -31,6 +31,9 @@ bool CheckSecurityStyle(int security_style) {
bool CheckSCTStatus(uint32_t sct_status) {
switch (sct_status) {
case net::ct::SCT_STATUS_LOG_UNKNOWN:
+ // INVALID is deprecated and should not be used anymore, but it
+ // might have been previously written into the disk cache.
+ case net::ct::SCT_STATUS_INVALID:
case net::ct::SCT_STATUS_INVALID_SIGNATURE:
case net::ct::SCT_STATUS_OK:
case net::ct::SCT_STATUS_INVALID_TIMESTAMP:
« no previous file with comments | « chrome/browser/ui/website_settings/website_settings.cc ('k') | content/common/ssl_status_serialization_unittest.cc » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698