Re:HTTP/2 is not the future, it’s the present
by tuukkah on Wednesday April 12, 2017 @11:24AM
(#14098559)
What's the support for HTTP/2 in tools like curl and socat?
Re:HTTP/2 is not the future, it’s the present
by syncsynchalt on Wednesday April 12, 2017 @01:15PM
(#14099679)
<strike>None for netcat (it's a bare-wire tool, and doesn't support HTTP/1.1 either)</strike>
sorry, I must have misread "socat" as "netcat". Since socat's HTTP integration is an HTTP proxy on port 8080 it should be transparent due to using "CONNECT" for https.
curl offers --http2 and uses ALPN where available as explained here: https://curl.haxx.se/docs/http2.html
Re:HTTP/2 is not the future, it’s the present
by martinflack on Wednesday April 12, 2017 @01:59PM
(#14100083)
Try h2i too: https://github.com/bradfitz/http2/tree/master/h2i
So I've noticed exactly 0 difference in my workflow between HTTP 1 and HTTP 2.