> The point is not that origin servers need to be upgraded, it's that clients and intermediaries should not be forced to upgrade. And HTTP2 doesn't require the

> The point is not that origin servers need to be upgraded, it's that clients and intermediaries should not be forced to upgrade. And HTTP2 doesn't require these upgrades? Clients and caching servers all need to support the new protocol. > That means the actual content of the web (HTML pages) should not require revision to support the wire protocol upgrade, Why would they? I'm not sure why the content matters in this discussion. > And then you look up the spec for how to interpret and/or resolve the rest of the URI. That may or may not involve a mapping to a wire protocol (e.g. the "about" scheme, or the "geo" scheme). OK, fair enough. How does this change my point though? HTTP vs HTTP2 requires a change in how the client "interpret[s] and/or resolve the rest of the URI."