Bring back SCT_STATUS_INVALID for cached entries
https://codereview.chromium.org/2241213002/ split SCT_STATUS_INVALID into two new enum values to record the different reasons that an SCT might be invalid. However, we didn't realize that SCT_STATUS_INVALID might still be present in disk cache entries, resulting in renderer kills when the browser tries to deserialize SSLStatus objects containing these cached SCT_STATUS_INVALID values. This CL brings back SCT_STATUS_INVALID and documents it as deprecated, but still existent for the sake of cache entries. BUG=640296 Review-Url: https://codereview.chromium.org/2277653002 Cr-Commit-Position: refs/heads/master@{#414280}
Showing
Please register or sign in to comment