# Outgoing partial links -\> https (on the fly)? - NOT http
**URL:** https://meta.discourse.org/t/outgoing-partial-links-https-on-the-fly-not-http/291374
**Category:** Self-hosting
**Created:** [January 12, 2024, 12:27am UTC](https://meta.discourse.org/t/outgoing-partial-links-https-on-the-fly-not-http/291374 "2024-01-12T00:27:58Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@mitchd](https://meta.discourse.org/u/mitchd)
#### Post date: [January 12, 2024, 12:27am UTC](https://meta.discourse.org/t/outgoing-partial-links-https-on-the-fly-not-http/291374/1 "2024-01-12T00:27:58Z")
Is there some way the back-end can turn all partial links in posts ( [example.com](http://example.com) ) into https links ( [https://www.example.com](https://www.example.com) )??
As it seems that they are made into http:// links, which leads to all sorts of mess when [http://example.com](http://example.com) outgoing requests fail for many users clicking-on from the post.
( Or, check the generated target address and amend to the correct protocol to get there? )
Thanks, first question, sorry if repeat but I can’t see anything succinctly this.
mitch
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [January 13, 2024, 12:59pm UTC](https://meta.discourse.org/t/outgoing-partial-links-https-on-the-fly-not-http/291374/2 "2024-01-13T12:59:40Z")
It seems like it’s time to make those links https by default. This might be a feature request.
---
### Author:  [@Jagster](https://meta.discourse.org/u/Jagster)
#### Post date: [January 13, 2024, 2:55pm UTC](https://meta.discourse.org/t/outgoing-partial-links-https-on-the-fly-not-http/291374/3 "2024-01-13T14:55:22Z")
Please no. Out there is a lot of sites that are using http, because they just don’t need SSL.
Would this be another casual job for search&replace? Or am I misunderstanding everything **again**?
> **irrational panic attack**
>
> Plus I’m worrying kind of edge situation where Discourse is using its own VPS and front of it is another VPS where is reverse proxy. Those will talk to each other without SSL quite often.
>
> But that is totally different situation, right? But I start to be a bit jumpy everytime there is something default that can change for me familiar abbreviations…
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [January 13, 2024, 3:07pm UTC](https://meta.discourse.org/t/outgoing-partial-links-https-on-the-fly-not-http/291374/4 "2024-01-13T15:07:15Z")
I think you’re wrong that those sites don’t need https. There is no excuse not to make your site secure now.
But it looks like I’m wrong that this should be a feature request. The browser rather than discourse should handle forcing to https.
> **[Towards HTTPS by default](https://blog.chromium.org/2023/08/towards-https-by-default.html?m=1)**
>
> For the past several years, more than 90% of Chrome users' navigations have been to HTTPS sites, across all major platforms. Thankfully, th...
---
### Author:  [@Arkshine](https://meta.discourse.org/u/Arkshine)
#### Post date: [January 13, 2024, 3:15pm UTC](https://meta.discourse.org/t/outgoing-partial-links-https-on-the-fly-not-http/291374/5 "2024-01-13T15:15:51Z")
I’m pretty sure that modern browsers prioritize HTTPS over HTTP by default.
Also, many websites server-side will redirect to HTTPS or use [HSTS](https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security) header.
---
### Author:  [@Jagster](https://meta.discourse.org/u/Jagster)
#### Post date: [January 13, 2024, 3:56pm UTC](https://meta.discourse.org/t/outgoing-partial-links-https-on-the-fly-not-http/291374/6 "2024-01-13T15:56:48Z")
> [@pfaffman](#):
>
> I think you’re wrong that those sites don’t need https. There is no excuse not to make your site secure now.
I don’t think I am wrong when we are talking about reality.
Need for securing connections between servers using SSL when data is not including anything that need to secure is worth of another topic. But is totally off topic here, though.
But saying to users that sorry, you can’t link because 3rd party isn’t using port 443 is just bad idea. It is not admin’s or not even discourse’s job to say what someone should or must do.
> [@Arkshine](#):
>
> I’m pretty sure that modern browsers prioritize HTTPS over HTTP by default.
Yes if it is there. And some household routers/modems are configured to use only https and that is actually really annoying. Because not every site follows Google’s want to use SSL everywhere and partly hecause so many platform serves old links using http and those stubid boxes can’t rewrite url.
So before any feature discussion there should be another meta topic first: is it responsibility of forum platform force to use SSL for outbound links.
After that technical solution is reasonable easy, I reckon — but again, I’m not a dev.
But back to topic.
So search&replace isn’t acute solution? But I don’t follow now… **again** … is the real issue how Discourse automatically forms links if just plain url is given? Is so, then I backup a little and yes, automatically there should be https — but it must be editable.
---
### Author:  [@mitchd](https://meta.discourse.org/u/mitchd)
#### Post date: [January 15, 2024, 12:32am UTC](https://meta.discourse.org/t/outgoing-partial-links-https-on-the-fly-not-http/291374/7 "2024-01-15T00:32:25Z")
Checking if http (and https with a similar function) is possible, using just the head of the target page, code copied from:
>
```plaintext
def check_http_url(url):
HTTP_URL = f'http://{url}'
try:
HTTP_URL = urlparse(HTTP_URL)
connection = HTTPConnection(HTTP_URL.netloc)
connection.request('HEAD', HTTP_URL.path)
if connection.getresponse():
return True
else:
return False
except:
return False
```
So with that (translated to Ruby if I recall), Discourse back-end could find out if the target of a partial link given in a post is https or http, then (with a preference for https) open the correct target link for the user?