> Both still leave the original text based protocol and would stop ISP header injection.
SSL is not a text-based protocol.
Neither is TCP, but that's just a wrapper.
Inside the SSL/TLS wrapper it is still just HTTP.
It's no longer 'in the clear' but it is still very much a text based protocol.
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.
Both still leave the original text based protocol and would stop ISP header injection.
Another defense against such trickery would be a legal one: make it illegal to tamper with data sent between two peers on the internet.
Imagine the postal service opening your mail and changing a couple of words in your mail just because they could.