To switch from http to https
Permalink 2 users found helpful
Hi There,
I need to activate SSL encryption to switch from http to https on my page.
Would you contact me and help, please? I offer £50 for this job done safely.
# concrete5 Version
Core Version - 5.7.5.13
Version Installed - 5.7.5.10
Database Version - 20160615000000
I need to activate SSL encryption to switch from http to https on my page.
Would you contact me and help, please? I offer £50 for this job done safely.
# concrete5 Version
Core Version - 5.7.5.13
Version Installed - 5.7.5.10
Database Version - 20160615000000
I haven't ordered it yet but it's possible to generate in CP of the server. Are you available to meet and fix it over the Skype?
Yes sure, look me up on Skype.
I have done it, waiting for your replay
So there are many posts, both on this site and elsewhere, about this issue. Many different answers that the authors describe as maybe works. However, there is no definitive answer, and nothing in the official documentation (that I can find) on this. So please expand on your answer. Specifically:
What if anything should be in the Canonical and Alternative Canonical entries?
Does checking the Render only at Canonical render at both of the above entries?
Does it automatically force an http reference to https, or should that automatically happen in the browser?
If not, how does one force this for both the domain name and the www alternate?
Should one check the Add Tag, and why or why not?
Can all of this be added to the actual documentation?
What if anything should be in the Canonical and Alternative Canonical entries?
Does checking the Render only at Canonical render at both of the above entries?
Does it automatically force an http reference to https, or should that automatically happen in the browser?
If not, how does one force this for both the domain name and the www alternate?
Should one check the Add Tag, and why or why not?
Can all of this be added to the actual documentation?
As far as I know, the Canonical and Alternative Canonical entries are for including meta data on pages i.e. adding a <link rel=”canonical” href=www.yoursite.com /> which indicates to search engines which of version of your site (http vs. https vs. www. vs. no W’s etc.) is the ‘main’ one.
These fields wont actually change the way your site works at all, only how Google interprets it. Note the Add Tag checkbox will include that meta tag on every page so I’m not honestly sure if using the Canonical/Alt Canonical fields will do anything at all without it.
Checking the Render box will prevent the site from loading out with the specified canonical URLs i.e. if you specify ‘www.yoursite.com’ as the canonical and check render, the site will simply refuse to load (503?) at e.g. yoursite.com orhttp://www.yoursite.com etc.
The automatic forcing http to https should be done on your host server with the .htaccess file in the root directory or your hosting may offer a nice single click solution. If you don’t have a .htaccess file in the root, add one by creating a text file and calling it .htaccess. There are various ways to do what you want and the exact code depends on your server type/version but you might find these work on an Apache setup:
#Force use WWW
RewriteCond %{HTTP_HOST} !^www\.
RewriteRule ^(.*)$https://www.%{HTTP_HOST}%{REQUEST_URI}... [L,R=301]
#Force remove WWW
RewriteCond %{HTTP_HOST} ^www\.(.+)
RewriteCond %{HTTPS}s/%1 ^(on(s)|offs)/(.+)
RewriteRule ^ http%2://%3%{REQUEST_URI} [L,R=301]
#Force use HTTPS
RewriteCond %{HTTPS} off
RewriteRule ^(.*)$https://%{HTTP_HOST}%{REQUEST_URI}... [L,R=301]
Hope that helps!
These fields wont actually change the way your site works at all, only how Google interprets it. Note the Add Tag checkbox will include that meta tag on every page so I’m not honestly sure if using the Canonical/Alt Canonical fields will do anything at all without it.
Checking the Render box will prevent the site from loading out with the specified canonical URLs i.e. if you specify ‘www.yoursite.com’ as the canonical and check render, the site will simply refuse to load (503?) at e.g. yoursite.com orhttp://www.yoursite.com etc.
The automatic forcing http to https should be done on your host server with the .htaccess file in the root directory or your hosting may offer a nice single click solution. If you don’t have a .htaccess file in the root, add one by creating a text file and calling it .htaccess. There are various ways to do what you want and the exact code depends on your server type/version but you might find these work on an Apache setup:
#Force use WWW
RewriteCond %{HTTP_HOST} !^www\.
RewriteRule ^(.*)$https://www.%{HTTP_HOST}%{REQUEST_URI}... [L,R=301]
#Force remove WWW
RewriteCond %{HTTP_HOST} ^www\.(.+)
RewriteCond %{HTTPS}s/%1 ^(on(s)|offs)/(.+)
RewriteRule ^ http%2://%3%{REQUEST_URI} [L,R=301]
#Force use HTTPS
RewriteCond %{HTTPS} off
RewriteRule ^(.*)$https://%{HTTP_HOST}%{REQUEST_URI}... [L,R=301]
Hope that helps!
Thank you. This is all quite useful. Some of the other threads had random experiments with the Canonical fields and so forth in addition to .htaccess modification rather than just focusing on .htaccess, which is all that really needs to change (and yes, your example works perfectly).
Lack of documentation can easily kill a good product. Forums can inform on what should be documented/clarified, but are not documentation. People seem to confuse the two.
Lack of documentation can easily kill a good product. Forums can inform on what should be documented/clarified, but are not documentation. People seem to confuse the two.
The 2 URLs are used in 2 ways.
1. The only render checkbox uses them for security measures (uncheck before moving a site or on a development server).
2. If the Add tag is checked, the Canonical URL is used in the meta tag page render output (followed by the URL slug)..
If you are forcing SSL and removing www. you only need the Canonical one set to https: //yoursite.com (leave the Alternate empty). If you want both (not recommended) use https: //www.yoursite.com in the Alternate).
[Note: the c5 editor is changing https to http, so there are no spaces after https: above]
Here's how I remove www. and force SSL in .htaccess (on many different server configurations):
1. The only render checkbox uses them for security measures (uncheck before moving a site or on a development server).
2. If the Add tag is checked, the Canonical URL is used in the meta tag page render output (followed by the URL slug)..
If you are forcing SSL and removing www. you only need the Canonical one set to https: //yoursite.com (leave the Alternate empty). If you want both (not recommended) use https: //www.yoursite.com in the Alternate).
[Note: the c5 editor is changing https to http, so there are no spaces after https: above]
Here's how I remove www. and force SSL in .htaccess (on many different server configurations):
<IfModule mod_rewrite.c> RewriteEngine On RewriteBase / # -- force SSL and remove www RewriteCond %{HTTP_HOST} ^www\. [NC,OR] RewriteCond %{HTTPS} off RewriteCond %{HTTP_HOST} ^(?:www\.)?(.+)$ [NC] RewriteRule ^ https://%1%{REQUEST_URI} [R=302,L,NE] # -- concrete5 pretty URLs # ... </IfModule>
Hello There,
I'd Glad to assit you.
Pm Sent with details, please check.
Thanks and Regards
Carter W
I'd Glad to assit you.
Pm Sent with details, please check.
Thanks and Regards
Carter W
Do you have a cert and you want to get C5 to go to Https?
If so look at the URL and redirect settings in the dashboard.