News for hackers. Stuff that matters.
Re:HTTP/2 is not the future, it’s the present by atonse on Wednesday April 12, 2017 @10:30AM (#14098005)
It's a common argument that HTTP/2 being binary makes it harder to debug. Sure, it might be tougher if I'm using Wireshark to look at raw TCP packets. But Chrome/Safari/Firefox/IE Web Inspectors (what most web devs use to debug HTTP requests) already parse the HTTP the same way as before.

So I've noticed exactly 0 difference in my workflow between HTTP 1 and HTTP 2.

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)
Re:HTTP/2 is not the future, it’s the present by tuukkah on Wednesday April 12, 2017 @11:55AM (#14098911)
Answering myself: curl has supported HTTP/2 since 2013.