HTTPS support for custom domains


#1

Is there any plan to support HTTPS for custom domains?

As the docs say accessing edit-content.com via a CNAME currently gives a certificate error.

This could be overcome by having certificates issued for custom domains; would that be worth the effort?

Although the docs suggest that HTTPS is not required, it’s slowly becoming the default across the web. In our case we can’t use our custom domain at all (without a certificate error), since the domain is HSTS preloaded.


#2

We’re looking into making this possible in 6.0, possibly through CloudFlare. No ETA on that release just yet.


#3

Nice, thank you. :slight_smile: