Fix recording metrics about HTTP migration process
This CL fix the way that of considering that HTTP credentials have no match, equivalent and conflicting HTTPS credentials added in https://crrev.com/c/1163243/. Starting with this CL we consider HTTP credential as no match, HTTP credentials for which no HTTPS credential for the same signon-realm (excluding the protocol), PasswordForm::Scheme (i.e. HTML, BASIC etc.) and username exists in Password Store. We consider HTTP credentials as having equivalent HTTPS credentials if they have same signon-realm (excluding the protocol), PasswordForm::Scheme, username and password. We consider HTTP credentials as having conflicting HTTPS credentials if they have same signon-realm (excluding the protocol), PasswordForm::Scheme and username but different password. Bug: 871140 Change-Id: If28c60f0a42f288c1f20a61f35c848978da39b49 Reviewed-on: https://chromium-review.googlesource.com/1196342 Commit-Queue: Narcis Gemene <gemene@google.com> Reviewed-by:Jan Wilken Dörrie <jdoerrie@chromium.org> Cr-Commit-Position: refs/heads/master@{#587640}
Showing
Please register or sign in to comment