Move to HTTPS by default to fix "Find Current Location" in Chrome 53+ about cambridge_voting_locations HOT 10 CLOSED

If we ( @WheresHJ ) switch our domain to this DNS below, it will start using Cloudflare and gain SSL. I can change the email of the cloudflare account (and password) if you tell me which one to use.

Change Nameservers to:

ns1.iwantmyname.net becky.ns.cloudflare.com
ns2.iwantmyname.net cody.ns.cloudflare.com
ns3.iwantmyname.net Remove this nameserver
ns4.iwantmyname.net Remove this nameserver

from cambridge_voting_locations.

Does https://letsencrypt.org work for us?

from cambridge_voting_locations.

I use LetsEncrypt on my personal server. It is awesome. I have a cronjob that renews it every 90 days as required and updates nginx. I don't think that is something we want in this case though.
Cloudflare is a top-100 standard service that (amongst other things) takes care of details and adds encryption to github sites as an overlay. It should solve our issue for our essentially client side app.

from cambridge_voting_locations.

Moving from github pages to heroku is another viable solution which would also give us HTTPS at some minor technical cost.

from cambridge_voting_locations.

@beechnut and I just changed these nameservers. Let us know if this was successful @thadk .

from cambridge_voting_locations.

Ahh nonstop class today forgot it was Tuesday and double booked. I'll keep an eye on it and do what I can from the Cloudflare. Right now it is still redirecting.

from cambridge_voting_locations.

@thadk your DNS might be cached - I tried it just now, and instead of getting an untrusted cert issue (which I seem to remember getting before), I got "This site can’t provide a secure connection - votecambridge.com sent an invalid response."

from cambridge_voting_locations.

I just told Cloudflare to rescan, and it says we should try again in a couple hours.

from cambridge_voting_locations.

Hurray:

Full (strict) instead of "Full" does not work because Github does not have a valid certificate.

I followed the instructions at https://blog.cloudflare.com/secure-and-fast-github-pages-with-cloudflare/ to add a "Page Rule" so that people using HTTP are forwarded to HTTPS so they can always use the "locate me" API.

from cambridge_voting_locations.

Looks good to me! Thanks so much to @thadk @WheresHJ and @beechnut for getting this knocked out. 🤘

from cambridge_voting_locations.