Force HTTPS always active by default

nsevimov

Is it possible to automatically enable the 'force https' option after generating a valid let's encrypt.

AdamM

grradmin

Shaijee

It's helpful. +1

Peertje

Kapa

Adam

The problem is that this setting can sometimes cause redirect loops, for example if you have an external proxy which is forwarding traffic on http - Enhance will then try to redirect to https:// and the proxy will bounce the request back to http:// causing an infinite loop. I think it needs to be a deliberate choice by the user to prevent excessive support tickets.

nsevimov

Adam
Yes in this case will be a huge problem but i think i know perfect solution for this.

In 'Platform' page to have switch button for Force HTTPS (this button force https to websites only if they have valid Let's Encrypt)
In 'Overrides' page to have switch button for Force HTTPS (this button can deactivate - reactivate force https)

Like that we will be able to deactivate it only for specific website, because i'm sure there is more than 1% who will use external proxy in shared hosting.

(Right now i activate force https manually for every new client, website)

josedieguez

Another loop case, is wordpress websites wich has their URLs wrongly configured as HTTP://, and you have on the panel or .htaccess forced the HTTPS

and you get a loop.

nsevimov

josedieguez

slimx

Interesting.
You're afraid that you'll get 1, 2 extra tickets but you're not afraid to damage your clients SEO.
Great perspective! Congratulations.

Lest you think I am arguing with you, I will develop my thesis:

The chance of getting a loop is 1/1000 i.e. 1 customer can probably have this problem out of 1000 customers.
The chances of hurting your clients SEO is 1000/1000.

When you do not forward HTTP to HTTPS then Google and all other search engines take all pages from HTTP and HTTPS as duplicates and thus prevents their indexing and therefore the optimization for serps.

Whether this will be done in future versions or not I will continue to manually crawl each new client to make sure that their sites reference HTTPS and do not have HTTP/HTTPS duplicate pages.

Success.

slimx

Yes unfortunately I MINUS1 this. -1

josedieguez

nsevimov

"you are afraid"

dude, i just told everyone another case that causes loop.

i haven't say this is a must, this is a minus, nor if positive or negative s:

"great perspective" wow... i'll keep my opinions for myself then s:

slimx

Your thesis is just assuming you know anything about anyone else's business :/

We are all allowed to share our opinions here, just like you are allowed to share your requests here.
Here's my thesis:
For starters majority of the websites you deploy (using Enhance) would most likely be on a CMS of some sort considering it is a hosted "hosting platform". The CMS by default would setup the site on https://, so your theory is completely wrong.

Allowing the client to have the ability to turn this feature on at their own accord is much better.

--
You're over-invested in the SEO mind-games everyone is playing. Never forget; SEO is 99% about speculation. Cause any case-studies you see become invalid after one random google update.

nsevimov When you do not forward HTTP to HTTPS then Google and all other search engines take all pages from HTTP and HTTPS as duplicates and thus prevents their indexing and therefore the optimization for serps.

Open search console and show me these "duplicates" lol. This is false, what on earth kinda site are you deploying for it to be double-indexed. If the site is HTTP it won't be an indexed anymore is what google stated MANY MANY YEARS ago.

FabioP

+1 for me.