Yes, just checking. I think we had this conversation few years ago too. I guess a CNAME is not enough? Doesn't in that case the address change from http://clojure.fi to http://clojurefinland.github.io too?
Ahh yeah the problem would be that ssl-cert in github pages wouldn’t be valid for http://clojure.fi I guess. So maybe we’re happy the way it is atm. 🙂
The redirect seems to be coming from an nginx server though… So it could proxy the request to github pages but still there should be a valid SSL-certificate for http://clojure.fi on the nginx server and that costs 💰.
Still it’s some 💰 in terms of work
But good point about letsencrypt!
But also, DNS changes to point the domain to github would work and github will handle the certificate.
Hmm okay so in DNS terms what should be done?
I mean, I can try to make something happen.
Now I tried https://clojure.fi for the first time. I see the problem right there.
apex http://clojutre.fi A records pointing to 185.199.108.153 185.199.109.153 185.199.110.153 185.199.111.153 (or ALIAS record to http://clojurefinland.github.io if the provider supports it) and www CNAME record to http://clojurefinland.github.io
I asked for a valid certificate to http://clojure.fi . Should happen at some point.
New cert has been installed, https://clojure.fi should now work without problems?
It still redirects to http://clojurefinland.github.io ? 😮
curl -v <https://clojure.fi>
* Trying 62.165.154.49...
* TCP_NODELAY set
* Connected to <http://clojure.fi|clojure.fi> (62.165.154.49) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/ssl/cert.pem
CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN, server accepted to use http/1.1
* Server certificate:
* subject: CN=<http://clojure.fi|clojure.fi>
* start date: Jun 12 08:42:08 2020 GMT
* expire date: Sep 10 08:42:08 2020 GMT
* subjectAltName: host "<http://clojure.fi|clojure.fi>" matched cert's "<http://clojure.fi|clojure.fi>"
* issuer: C=US; O=Let's Encrypt; CN=Let's Encrypt Authority X3
* SSL certificate verify ok.
> GET / HTTP/1.1
> Host: <http://clojure.fi|clojure.fi>
> User-Agent: curl/7.64.1
> Accept: */*
>
< HTTP/1.1 301 Moved Permanently
< Server: nginx/1.14.2
< Date: Fri, 12 Jun 2020 18:23:07 GMT
< Content-Type: text/html
< Content-Length: 185
< Connection: keep-alive
< Location: <https://clojurefinland.github.io/>
< Strict-Transport-Security: max-age=31536000
<
<html>
<head><title>301 Moved Permanently</title></head>
<body bgcolor="white">
<center><h1>301 Moved Permanently</h1></center>
<hr><center>nginx/1.14.2</center>
</body>
</html>
* Connection #0 to host <http://clojure.fi|clojure.fi> left intact
* Closing connection 0
➜ <http://ClojureFinland.github.io|ClojureFinland.github.io> git:(master) ✗
It would be super cool if you could add something like this to nginx
conf:
location / {
proxy_pass <https://clojurefinland.github.io>;
}
I personally don't find any value in that proxying
Ok, I think the idea was that it would look maybe “more professional” if the address bar said http://clojure.fi
But It’s not a biggie to me at least.
if it's the truth, I.e. github is hosting it then I think it's good
more likely that someone will notice they can contribute?
The page has link to github
tthat's why I said more likely