search

johnwcowan / r7rs-work

96 stars 12 forks source link

https and user-friendliness of the r7rs URLs. #29

Open ghost opened 2 years ago

ghost commented 2 years ago

At the moment the following urls would be expected of the r7rs project. The checkmark means that the URL exists and is working in an expected way.

What needs to be done to implement the websites now working at the moment?

lassik commented 2 years ago

With permission from @arthurgleckler, I suggest turning all of the subdomains into DNS CNAME speechcode.com which is his server. small.r7rs.org already points there. Arthur is active and skilled with HTTP and DNS, so he can maintain the necessary redirects.

lassik commented 2 years ago

Better yet, point the root r7rs.org at his server (via A and AAAA records, to conform to internet standards) and make all the subdomains CNAME to the root domain.

arthurgleckler commented 2 years ago

@johnwcowan, what's your opinion? I believe that John started r7rs.org. I just set up small.r7rs.org.

johnwcowan commented 2 years ago

http://r7rs.org points to https://github.com/johnwcowan/r7rs-work/blob/master/R7RSHomePage.md. It would be good if https://r7rs.org, http://www.r7rs.org, and https://www.r7rs.org pointed to the same place. I have no control over this.

I don't think that large.r7rs.org makes much sense at this stage.

On Wed, Aug 3, 2022 at 4:28 PM Arthur A. Gleckler @.***> wrote:

@johnwcowan https://github.com/johnwcowan, what's your opinion? I believe that John started r7rs.org. I just set up small.r7rs.org.

— Reply to this email directly, view it on GitHub https://github.com/johnwcowan/r7rs-work/issues/29#issuecomment-1204441388, or unsubscribe https://github.com/notifications/unsubscribe-auth/AANPPBVGDXJJEHX2XRSPJ6DVXLI7XANCNFSM55NGKMGA . You are receiving this because you were mentioned.Message ID: @.***>

arthurgleckler commented 2 years ago

On Wed, Aug 3, 2022 at 1:46 PM John Cowan @.***> wrote:

http://r7rs.org points to https://github.com/johnwcowan/r7rs-work/blob/master/R7RSHomePage.md. It would be good if https://r7rs.org, http://www.r7rs.org, and https://www.r7rs.org pointed to the same place. I have no control over this.

I don't think that large.r7rs.org makes much sense at this stage.

Adding CPH and JAR. Would it be possible to add these redirects — and, perhaps, TLS/SSL using Let's Encrypt? I can help with the latter.

Message ID: @.***>

arthurgleckler commented 2 years ago

I can change DNS records, which will probably be needed for TLS, but I don't know what they should be set to.  Currently gandi is giving us a port 80 302 redirect from their redirect service to a URL I can configure, but that's not going to work for TLS.

I have set up Let's Encrypt in the past but have forgotten all about it. If that's going to happen I think someone else will have to figure out how. Taylor Campbell knows all about this and has been taking care of Let's Encrypt TLS on mumble.net. I could ask him for help but don't know if he'll be willing.

On 8/8/22 3:02 PM, Arthur A. Gleckler wrote:

On Wed, Aug 3, 2022 at 1:46 PM John Cowan @. @.>> wrote:

http://r7rs.org points to
https://github.com/johnwcowan/r7rs-work/blob/master/R7RSHomePage.md.
It
would be good if https://r7rs.org, http://www.r7rs.org, and
https://www.r7rs.org pointed to the same place. I have no control over
this.

I don't think that large.r7rs.org <http://large.r7rs.org> makes
much sense at this stage.

Adding CPH and JAR.  Would it be possible to add these redirects — and, perhaps, TLS/SSL using Let's Encrypt?  I can help with the latter.

Message ID: ***@***.***>
arthurgleckler commented 2 years ago

On Wed, Aug 10, 2022 at 7:11 AM Jonathan A Rees @.***> wrote:

I can change DNS records, which will probably be needed for TLS, but I don't know what they should be set to. Currently gandi is giving us a port 80 302 redirect from their redirect service to a URL I can configure, but that's not going to work for TLS.

I have set up Let's Encrypt in the past but have forgotten all about it. If that's going to happen I think someone else will have to figure out how. Taylor Campbell knows all about this and has been taking care of Let's Encrypt TLS on mumble.net. I could ask him for help but don't know if he'll be willing.

I've done it before, but not on a site served by Github, which is what John is using for r7rs.org. On a regular site, the key is to install a file that Let's Encrypt provides that is used to prove that one controls the site. I've found this page for doing it with Github, but it's for the Github Pages feature, not regular Github pages (lower case) like John uses:

https://docs.github.com/en/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https

Message ID: @.***>

I don't have time to work on this now, but if Lassi or someone else can figure out the details, I'll help.