Rainbows! Rack HTTP server user/dev discussion
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: rainbows-public@bogomips.org
Subject: website move to HTTPS
Date: Mon, 31 Oct 2016 20:34:46 +0000	[thread overview]
Message-ID: <20161031203446.GA15409@starla> (raw)

Let's Encrypt seems to be working well for several months, now;
and I don't think it's a good idea to let spies know details of
your stack, so HTTPS access is available.

website: https://bogomips.org/rainbows/
list archives: https://bogomips.org/rainbows-public/

Note: I'm also dropping the rainbows.bogomips.org subdomain to
reduce subjectAltName bloat (and associated negotiation times).
Unencrypted HTTP will remain available indefinitely for folks
on old, un-upgradeable systems.

https://bogomips.org/rainbows.git/patch?id=50e91f1ac0cd
Author: Eric Wong <e@80x24.org>
Date:   Mon Oct 31 20:27:00 2016 +0000

    doc: Static_Files: remove Future section

    sendfile(2) is fewer syscalls and FDs than splice(2),
    and an open-file-cache is unlikely to be worth the complexity.

https://bogomips.org/rainbows.git/patch?id=4932b06f1391
Author: Eric Wong <e@80x24.org>
Date:   Mon Oct 31 20:13:40 2016 +0000

    doc: move homepage and update URLs to HTTPS

    Let's Encrypt is working well for us and having fewer domains
    reduces subjectAltName bloat to speed up connection
    establishment

    HTTP will remain working indefinitely since some old systems
    do not have modern TLS stacks.

                 reply	other threads:[~2016-10-31 20:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://yhbt.net/rainbows/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20161031203446.GA15409@starla \
    --to=e@80x24.org \
    --cc=rainbows-public@bogomips.org \
    --subject='Re: website move to HTTPS' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this inbox:

	../../rainbows.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).