Closed lcreid closed 7 years ago
We decided to redirect both to weenhanceit.com.
Github pages with a custom domain doesn't support HTTPS (for reasons that make sense if you think about it -- how would they support everyone setting up their own certificates?). Redirecting HTTPS to HTTP isn't cool, so we could only redirect HTTP.
But then one of the suggestions to Github pages is to use a proxy for the custom domain, and have it proxy to the .github.io
domain, which does support HTTPS (they have a wildcard certificate for *.github.io
). Since we already have a server redirecting, we could have it proxy instead, and force scheme to HTTPS.
So the Nginx default server would also be the server for weenhanceit.com. It would force HTTP to HTTPS, and would proxy requests to weenhanceit.github.io
over HTTPS.
So for now, we're going to redirect HTTP to the Github page, and create another issue for the longer term issue of serving our home page via HTTPS.
The current set-up returns a certificate error on one of the HTTPS enabled sites, if you request the site by IP over HTTPS. Possible solutions: