https://rust-lang.org doesn't work

[skade]

Accessing https://rust-lang.org/ leads to an "unable to connect" error.

http://rust-lang.org/ works and redirects to https://www.rust-lang.org.

A similar redirect should be in place for https.

[aidanhs]

We had a chat about this in an infra meeting - https://mozilla.logbot.info/rust-infra/20180130#c14214062-c14214171

18:25 acrichto www.rust-lang.org is a cloudfront hosted static site
18:25 acrichto rebuilt on each push to master branch of rust-www
18:25 acrichto rust-lang.org is a "DNS redirect"
18:25 acrichto which means that easydns, our provider, just hosts a thing that issues an http redirect
18:25 acrichto rust-lang.org doesn't work b/c easydns doesn't have certs for us
18:25 acrichto to implement this we'd need to point rust-lang.org to a location that has support for ssl certs

It's not obvious what the next steps should be, and we probably aren't going to be urgently pursuing a fix. That said, if anyone has recommendations on the best/easiest way to do this we'd be interested to hear your suggestions!

[davidalber]

This is a duplicate of #170.

[davidalber]

Similar to #165, I believe this can be addressed using Lambda@Edge. We can update the DNS record for rust-lang.org to point at d13ahrxq5gcaw8.cloudfront.net (like www.rust-lang.org) and use a lambda to redirect requests for rust-lang.org to www.rust-lang.org.

I've never used Lambda@Edge, so this is based on what I've read in the documentation. Some prototyping is needed. Also, the SSL certificate being used for https://www.rust-lang.org/ is only for www.rust-lang.org. We'd need to regenerate a new certificate that has both domains or a wildcard.

[gereeter]

This seems to be working for me.

[skade]

Closing as fixed.