From: Eric Wong <email@example.com> To: firstname.lastname@example.org Subject: website move to HTTPS Date: Mon, 31 Oct 2016 20:34:46 +0000 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 <email@example.com> 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 <firstname.lastname@example.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 index Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publically 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://bogomips.org/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 \ --email@example.com \ --firstname.lastname@example.org \ /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
Rainbows! Rack HTTP server user/dev discussion Archives are clonable: git clone --mirror https://bogomips.org/rainbows-public git clone --mirror http://ou63pmih66umazou.onion/rainbows-public Newsgroups are available over NNTP: nntp://news.public-inbox.org/inbox.comp.lang.ruby.rainbows nntp://ou63pmih66umazou.onion/inbox.comp.lang.ruby.rainbows note: .onion URLs require Tor: https://www.torproject.org/ or Tor2web: https://www.tor2web.org/ AGPL code for this site: git clone https://public-inbox.org/ public-inbox