Materialize: Feature Request : Add SSL to site
Description
Add SSL(https) Support to materializecss.com.
You can use openssl Lets Encrypt (Its Open Source).
vishnu1991
All 5 comments
Materialize is using github hosting in combination with a (I guess) DNS provider. Github hosting offers https but due to the custom domain the certificate is not valid. Maybe Materialize could switch to cloudflare, where a ssl certificate is free and included?
tomscholz
on 30 Dec 2016
There isn't any sensitive information that should be sent from either side on our website, so I don't think this is all that necessary.
Dogfalo
on 30 Dec 2016
https should be used by default. It works with Cloudflare and GitHub, see https://websectools.com and https://github.com/DanielRuf/WebSecTools
Modern browsers are pushing more and more to a https-only internet and many apps and search results often redirect to the https version which often causes issues if there is no valid TLS certificate ;-)
DanielRuf
on 30 Mar 2017
There isn't any sensitive information that should be sent from either side on our website, so I don't think this is all that necessary.
To quote an article at Googles Web Fundamentals
You should always protect all of your websites with HTTPS, even if they don鈥檛 handle sensitive communications.
Maybe (in the future) we should consider to move to netlify
See: https://macwright.org/2017/05/08/https.html & https://netlify.com
tomscholz
on 29 May 2017
I agree with @tomscholz this isn't a priority right now.
fega
on 30 May 2017
Related issues
PhillippOhlandt
路
3Comments
hartwork
路
3Comments
lpgeiger
路
3Comments
acierpinski
路
3Comments
samybob1
路
3Comments
Most helpful comment
https should be used by default. It works with Cloudflare and GitHub, see https://websectools.com and https://github.com/DanielRuf/WebSecTools
Modern browsers are pushing more and more to a https-only internet and many apps and search results often redirect to the https version which often causes issues if there is no valid TLS certificate ;-)