HTTP/2 won't stop anything. Encryption is not mandatory. Even if it were, browsers are going to be defaulting to HTTP 1.x on port 80 for perhaps a decade. Transparent proxying and downgrade attacks are still totally feasible. Just like every other step in Internet history, user security and privacy has been kicked to the curb.
https would stop injection just the same and is just http-over-ssl/tls. You could also simply sign the the content (but that would still allow wire-tapping).
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.
> 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.
For example, HTTP2 will stop ISP header injection such as this: http://www.propublica.org/article/somebodys-already-using-ve...