And HTTP2 is essentially just a multiplexed wrapper around HTTP1-like semantics, AFAICS.
I'm not an HTTP2 expert, but I would bet that WireShark can make an HTTP2 session look basically the same as a bunch of HTTP1 requests. It's the same "wrapper" concept except it adds multiplexing.
Yeah and once you multiplex, your text based protocol is gonna suck to read anyways. So in practice you'll use Wireshark, and then you no longer care if it's text based.
