Clean Obsolete HTTP Data from the Password Store

chrome/browser/password_manager/password_manager_util.h

Index: chrome/browser/password_manager/password_manager_util.h
diff --git a/chrome/browser/password_manager/password_manager_util.h b/chrome/browser/password_manager/password_manager_util.h
new file mode 100644
index 0000000000000000000000000000000000000000..3d8da0e9483a27450928fc60e273df747e0d105d
--- /dev/null
+++ b/chrome/browser/password_manager/password_manager_util.h
@@ -0,0 +1,29 @@
+// Copyright 2017 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+#ifndef CHROME_BROWSER_PASSWORD_MANAGER_PASSWORD_MANAGER_UTIL_H_
+#define CHROME_BROWSER_PASSWORD_MANAGER_PASSWORD_MANAGER_UTIL_H_
+
+class GURL;
+class Profile;
+
+namespace password_manager_util {
+
+// Checks whether HTTP Strict Transport Security (HSTS) is active for a given
+// profile for the host of the given origin.
+bool IsHSTSActiveForProfileAndHost(Profile* profile, const GURL& origin);
+
+// Cleans all obsolete HTTP data for a given profile. HTTP data is considered
+// obsolete, when the corresponding site has migrated to HTTPS and HSTS is
+// enabled. Data that will be cleaned includes passwords, blacklisted origins
+// and site statistics. This is guarded by a preference and will be a no-op if
+// the task was run for the profile in the past.
+void CleanObsoleteHttpDataForProfile(Profile* profile);

[vasilii, 2017/02/24 17:27:04]

I guess the function is public for the testing reasons.

[jdoerrie, 2017/02/27 10:53:21]

Yeah, I suppose I could add a delay field to
|DelayCleanObsoleteHttpDataForProfile| and call
|DelayCleanObsoleteHttpDataForProfile(profile, 0)| instead for tests.

[vasilii, 2017/02/27 12:28:26]

Acknowledged.

+
+// Delayed version of the above method.
+void DelayCleanObsoleteHttpDataForProfile(Profile* profile);
+
+}  // namespace password_manager_util
+
+#endif  // CHROME_BROWSER_PASSWORD_MANAGER_PASSWORD_MANAGER_UTIL_H_