Default typed omnibox navigations to https: Fix ports and IP addresses
Hostnames typed without a scheme but with a non-default port shouldn't be upgraded to HTTPS. In such a case, we can't simply change the scheme to https:// and expect the site to load since it's likely that the HTTPS version of the URL is also served from a non-default port. This CL also fixes handling of IP addresses when there is a port. Previously, we were checking whether the entered text was an IP address. This breaks down if the IP address has a port attached to it such as 127.0.0.1:8080. This CL instead checks the canonicalized_url. Bug: 1141691 Change-Id: Iffefa5c0ee939b361d8152c5cd417756841b5923 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2623683 Auto-Submit: Mustafa Emre Acer <meacer@chromium.org> Commit-Queue: Justin Donnelly <jdonnelly@chromium.org> Reviewed-by:Justin Donnelly <jdonnelly@chromium.org> Cr-Commit-Position: refs/heads/master@{#842552}
Showing
Please register or sign in to comment