Fork me on GitHub
Slack Archive

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

2020-06-12

Channels

#clojure-finland
<
2020-06-12
>
elahti04:06:49

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?

valtteri04:06:39

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. 🙂

valtteri04:06:22

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 💰.

valtteri05:06:22

Still it’s some 💰 in terms of work

valtteri05:06:17

But good point about letsencrypt!

juhoteperi05:06:49

But also, DNS changes to point the domain to github would work and github will handle the certificate.

elahti09:06:04

Hmm okay so in DNS terms what should be done?

elahti09:06:21

I mean, I can try to make something happen.

elahti09:06:22

Now I tried https://clojure.fi for the first time. I see the problem right there.

juhoteperi09:06:09

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

elahti09:06:21

I asked for a valid certificate to http://clojure.fi . Should happen at some point.

elahti09:06:48

New cert has been installed, https://clojure.fi should now work without problems?

valtteri18:06:41

It still redirects to http://clojurefinland.github.io ? 😮 

curl -v 
*   Trying 62.165.154.49...
* TCP_NODELAY set
* Connected to  (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=
*  start date: Jun 12 08:42:08 2020 GMT
*  expire date: Sep 10 08:42:08 2020 GMT
*  subjectAltName: host "" matched cert's ""
*  issuer: C=US; O=Let's Encrypt; CN=Let's Encrypt Authority X3
*  SSL certificate verify ok.
> GET / HTTP/1.1
> Host: 
> 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: 
< 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  left intact
* Closing connection 0
➜   git:(master) ✗

valtteri18:06:32

It would be super cool if you could add something like this to nginx conf: 

location / {
    proxy_pass  ;
}

Macroz18:06:56

I personally don't find any value in that proxying

valtteri18:06:18

Ok, I think the idea was that it would look maybe “more professional” if the address bar said http://clojure.fi

valtteri18:06:26

But It’s not a biggie to me at least.

Macroz18:06:57

if it's the truth, I.e. github is hosting it then I think it's good

Macroz18:06:23

more likely that someone will notice they can contribute?

valtteri18:06:48

The page has link to github

Macroz18:06:24

tthat's why I said more likely