RFC 2817:Upgrading to TLS Within HTTP/1.1
RFC-Ref

Hop-by-hop


Click on the red underlined text to get to the source

... As a hop-by-hop header, Upgrade is negotiated between each pair of HTTP counterparties. If a User Agent ...
... These scenarios also complicate diagnosis of a 426 response. Since Upgrade is a hop-by-hop header, a proxy that does not recognize 426 might remove ...
... This hop-by-hop definition of Upgrade was a deliberate choice. It allows for incremental deployment on either side of proxies ...


... Henrik Frystyk Nielsen, whose work on the Mandatory extension mechanism pointed out a hop-by-hop Upgrade still requires tunneling. ...



Google
Web
RFC-Ref