Change typed scoring for HTTP-to-HTTPS redirects
This CL follows on crrev.com/c/1002890, which added a new |incremented_omnibox_typed_score| column to the visits database. Modifies the interface to HistoryBackend::AddPageVisit() to take a boolean |should_increment_typed_count| parameter, and moves the decision on whether the |typed_count| should be incremented into the caller HistoryBackend::AddPage(). When there are redirects, AddPage() now checks if the first redirect is a simple HTTP to HTTPS redirect (that is, only the scheme if the URL changes, along with the addition or removal of trivial subdomains such as "www." or "m."), and if it is counts the HTTPS URL typed for incrementing the omnibox score, rather than the initial HTTP URL. This will cause the omnibox to learn to suggest the HTTPS URL directly. A followup CL will rename |typed_count| and related terms to |omnibox_typed_score| to clarify their meaning. Bug: 542484 Change-Id: I5edac0fd24f30230000b0fc7258e8c48b6a2e78c Reviewed-on: https://chromium-review.googlesource.com/1048826Reviewed-by:Sylvain Defresne <sdefresne@chromium.org> Reviewed-by:
Mark Pearson <mpearson@chromium.org> Commit-Queue: Christopher Thompson <cthomp@chromium.org> Cr-Commit-Position: refs/heads/master@{#565395}
Showing
This diff is collapsed.
Please register or sign in to comment