search

codeclubsocial / codeclub_website_dev

CodeClub website source (website no longer hosted)
http://www.codeclub.social
26 stars 7 forks source link

setup SSL for domain #32

Closed holaymolay closed 7 years ago

holaymolay commented 7 years ago

ssl is working: https://www.codeclub.social/

The only problem is if someone goes to www.codeclub.social it resolves as non-https...

holaymolay commented 7 years ago

ssl works but not all versions of the domain (e.g. www.codeclub.social) forward to https

Here's a fantastic solution: https://stackoverflow.com/a/23977269/3170942

craig429 commented 7 years ago

Notes on HTTPS redirection:

  1. Port 3000 (or process.env.PORT)is still open for development. It is HTTP. This gets turned off in production.
  2. Port 80 will redirect to port 443 using HTML code 301, which translates to: Moved Permanently. Details here: https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
  3. Once the redirect is encountered by accessing port 80 your browser will cache the redirect and automatically resolve an HTTP request to an HTTPS request on future accesses. This happens in Chrome, anyway. So for testing, if you need to hit the site at the HTTP port you will need to clear your browser cache first.

Closing this issue.

craig429 commented 7 years ago

I should also mention that the site certs key.pem and cert.pem are bogus since they haven't been signed by a CSA, so you will get "Not secure" warnings when you HTTPS to the site.

holaymolay commented 7 years ago

maybe I don't sufficiently understand SSL, but we are piggybacking on heroku's ssl Certificate. Also, I've not gotten the error you're talking about, that is unless the recent changes have changed that

craig429 commented 7 years ago

That sounds right. Probably cert.pem and key.pem are not even used on the Heroku side. I need them when I run locally.

holaymolay commented 7 years ago

just in case: https://jaketrent.com/post/https-redirect-node-heroku/