A there reasons to not allow http(s)-transparent autolinks like <//example.com>
?
This one works [//example.com](//example.com)
A there reasons to not allow http(s)-transparent autolinks like <//example.com>
?
This one works [//example.com](//example.com)
I wouldn’t mind disallowing scheme-relative links like that. They’re an anti-pattern. See https://github.com/konklone/cdns-to-https#conclusion-cdns-should-redirect-to-https.
When a resource is available over both HTTP and HTTPS, there is no reason not to always use the HTTPS version (and hardcode it in the URL).
There are contrary opinions on encrypting everything: HTTP/2.0 — The IETF is Phoning It In: Bad protocol, bad politics by Poul-Henning Kamp