URL verify default to https

The URL verifier defaults to https if a domain can be reached at https. This isn't always correct, especially with virtual hosts.

Example : I wanted to verify http://www.palsenberg.com, but the IP it resolved to also has some https hosts. https on www.palsenberg.com wasn't configured.
I wasn't able to complete the verification until the www.palsenberg.com was actually reachable over https.

No file or test is identified. Start by locating the URL verifier and reviewing how it selects HTTPS based on the resolved IP rather than the requested hostname. Reproduce the virtual-host case described in the issue, and consider the work complete when an HTTP URL is not forced to HTTPS solely because another host at the same IP supports it.

Written by the indexing model from the issue text.