# Make auto-linked URLs use HTTPS

**URL:** <https://meta.discourse.org/t/make-auto-linked-urls-use-https/285690>\
**Category:** Product Support\
**Created:** [November 16, 2023, 8:53am UTC](https://meta.discourse.org/t/make-auto-linked-urls-use-https/285690 "2023-11-16T08:53:14Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![Bas](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/bas/32/294929_2.png) [@Bas](https://meta.discourse.org/u/Bas)\
**Post date:** [November 16, 2023, 12:52pm UTC](https://meta.discourse.org/t/make-auto-linked-urls-use-https/285690/14 "2023-11-16T12:52:05Z")

</div>

> [@renem](#):
>
> can we change this behavior?

I don’t think you would want this.

> [@renem](#):
>
> HTTPS is pretty much the default nowadays:

While it’s certainly high, which is good, I don’t think that 85% is enough to change the default behaviour of your forum.

As far as I know, pretty much any (I’d bet on 99+%) https site will redirect all http requests to the https one.

The reverse does not hold true.

Meaning that linking to [http://example.com](http://example.com) is almost never a problem, since you end up on [https://example.com](https://example.com) anyway.

* * *

Like @Stephen , I think you might be focussing on the wrong part. As far as I know, having a `<a href="http...` link will not trigger the mixed content warnings.

This error should only be triggered by embedding non-https content into your https site. So loading external images could be a culprit, or embedding a third party script, something in a theme maybe?  
Probably good to dive deeper into the browser console and see what triggers the error 🙂

---

_[View the full topic](https://meta.discourse.org/t/make-auto-linked-urls-use-https/285690)._