# \<//example.com\> in autolinks?

**URL:** <https://talk.commonmark.org/t/example-com-in-autolinks/1100>\
**Category:** Spec\
**Created:** [March 10, 2015, 7:28pm UTC](https://talk.commonmark.org/t/example-com-in-autolinks/1100 "2015-03-10T19:28:15Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![vitaly](https://cdn.commonmark.org/user_avatar/talk.commonmark.org/vitaly/32/396_2.png) [@vitaly](https://talk.commonmark.org/u/vitaly)\
**Post date:** [March 10, 2015, 7:28pm UTC](https://talk.commonmark.org/t/example-com-in-autolinks/1100/1 "2015-03-10T19:28:15Z")

</div>

A there reasons to not allow http(s)-transparent autolinks like `<//example.com>`?

This one works `[//example.com](//example.com)`

---

<div class="post-metadata">

**Author:** ![mathias](https://cdn.commonmark.org/user_avatar/talk.commonmark.org/mathias/32/89_2.png) [@mathias](https://talk.commonmark.org/u/mathias)\
**Post date:** [March 12, 2015, 8:59am UTC](https://talk.commonmark.org/t/example-com-in-autolinks/1100/2 "2015-03-12T08:59:09Z")

</div>

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](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).

---

<div class="post-metadata">

**Author:** ![Brian\_Lalonde](https://cdn.commonmark.org/user_avatar/talk.commonmark.org/brian_lalonde/32/1565_2.png) [@Brian\_Lalonde](https://talk.commonmark.org/u/Brian_Lalonde)\
**Post date:** [March 13, 2015, 8:51pm UTC](https://talk.commonmark.org/t/example-com-in-autolinks/1100/3 "2015-03-13T20:51:27Z")

</div>

There are contrary opinions on encrypting everything: [HTTP/2.0 — The IETF is Phoning It In: Bad protocol, bad politics by Poul-Henning Kamp](http://queue.acm.org/detail.cfm?id=2716278)