bobray
May 28, 2019, 8:51pm
22
+1 for nuan88’s answer, http/https is the protocol and is not technically part of the domain name.
Using https should actually improve your link juice because Google (and I think some other engines) give higher scores to https sites.
All your internal links should be in the form of link tags:
<a href="[[~12]]">LinkText</a>
Where 12 is the ID of the resource you’re linking to.
If the server_protocol
System Setting is set to https, MODX should automatically create https links for those tags.
egmund
July 6, 2019, 11:36am
24
I had the same problem - not in my site, just a new page - ‘insisting’ on http.
Fortunately I noticed in another browser it was fine, so I closed and reopened my main browser (Opera) and all was fine: back to https.
1 Like
nuan88
July 7, 2019, 3:57pm
25
Yes you have to move extremely slowly when doing this, and test a lot before changing, lots of weird backsliding and sudden, new errors (not real errors just some call can’t connect or whatever)
markh
July 7, 2019, 9:49pm
26
In general it’s really quite simple to switch to HTTPS, and MODX will automatically pick up on the change.
Caches and hardcoded values really are the only things that can get in the way.
nuan88
July 7, 2019, 10:01pm
27
Yes its simple, but you wouldn’t believe the number of times everything looked ok…and then the next day it was broken. Not really broken but not the right icon in the browser.
So I just mean slow down and test it like crazy before you make changes.
tried that, but still no luck
I’m managing the following website: https://scsynergy.com
You can check the source code (header part of it) there I inserted the code to inspect what it generates and commented it out. See it attached.
the issue only lays here <base href="[[!++site_url]]" />
it simply does not set the protocol to https
all the internal links between pages are correctly set and work as expected.
but that’s not a solution
did you search for a system-setting or context-setting with the key ‘site_url’?
there is no system setting called “site_url”,
there is “server_protocol” instead, which is set to “https”
maybe a plugin, which does that?
which plugins do you have installed and active?
did you also check context-settings?
markh
July 9, 2019, 1:32pm
36
Is your server behind a reverse proxy that adds the SSL certificate while the origin server uses HTTP rather than HTTPS? Something like Cloudflare?
you are trying to use the .htaccess-file on a nginx-server?
oleksiy.ostapenko:
I’m managing the following website: https://mangazuki.online/
You can check the source code (header part of it) there I inserted the code to inspect what it generates and commented it out. See it attached.
Kindly tell me did you please search for the system-setting or contextual-setting with the key punk ‘site_url’?
zaigham
September 28, 2019, 4:54pm
41
I remember having similar situation and it seemed that MODX was confusing between http/https urls across website. That setup was load balanced/failover. To fix the issue I had to stop MODX figuring out http/https automatically.
To do that, I did the following:
in core/config.inc.php find:
$url_scheme= $isSecureRequest ? 'http://' : 'https://';
replace it with:
$url_scheme = 'https://';
Hope this will help you.
I believe, this is something you need to remember during upgrades as well.
1 Like
tempsur
September 24, 2021, 1:39pm
42
I had the same problem - not in my site, just a new page - ‘insisting’ on http..
esger
October 19, 2022, 9:52am
43
This happened to me as well on Modx cloud… after emptying the cache it went to https.