falcon

From my POV: > TLS requires ALPN. Supported by recent versions of Ruby pretty well, but as you say, older versions, not so well. > Setting up more advanced TLS is highly undocumented. It was slightly tricky with Ruby but it provides the appropriate callbacks and the documentation is reasonable: https://github.com/socketry/falcon/blob/940c25f4d19e9ad900ce... > How do you test TLS? I specifically solved this problem by using a self-signed local certificates and certificates store: https://github.com/socketry/async-rspec/blob/master/lib/asyn... That code makes appropriate contexts available for client and server in unit testing. Additionally I hacked this together: https://github.com/socketry/localhost It generates local self-signed certificates which you can easily use with a web browser. It solves the "localhost development via https" prob

So, I implemented https://github.com/socketry/falcon - a HTTP/1, HTTP/2 web server, including client. HTTP/2 in my opinion is simply a better protocol. It's more robust, and it has a binary framing layer which implements connection semantics separately from request/response headers. What I mean by this, is `content-length` or `transfer-encoding` are no longer used to control how the protocol actually works (i.e. how many bytes of data are consumed). I think this is a great step forward because it removes ambiguity and simplifies the overall protocol, and it's clear how extra features can be added in the future without impacting existing clients/servers - something that HTTP/1 struggled with a bit. I also think it impacts how we build web applications. I already wrote this as a blog post: https://www.codeotaku.com/journal/2018-10/http-2-fo