HTTP/1.1
Click on the red underlined text to get to the source
... IESG reaffirmed that the practice of issuing
parallel "secure" port numbers should be deprecated. The HTTP/1.1
Upgrade mechanism can apply Transport Layer Security [6 ...
... IP addresses to a single host, an
HTTP/1.1 server will use the Host: header to disambiguate the
...
... header to disambiguate the
intended web service. As HTTP/1.1 usage has grown more prevalent,
more ISPs are offering name-based ...
... hostname, relying exclusively on the IP address. Using a cleartext
HTTP/1.1 Upgrade: preamble to the TLS handshake -- choosing the
...
...
Either the client or server can use the HTTP/1.1 [1] Upgrade
mechanism (Section 14.42) to indicate that a TLS ...
...
When the client sends an HTTP/1.1 request with an Upgrade header
field containing the token "TLS ...
... token "TLS/1.0", it is requesting the server to
complete the current HTTP/1.1 request after switching to TLS/1.0.
...
... Connection header field (section 14.10) whenever
Upgrade is present in an HTTP/1.1 message".
...
...
Like any other pipelined HTTP/1.1 request, data to be tunneled may be
sent immediately after the blank line. The usual caveats also apply:
data may be discarded if the eventual response is negative, and the
...
... Fielding, R., Gettys, J., Mogul, J., Frystyk, H., Masinter, L., Leach, P. and T. Berners-Lee, "Hypertext Transfer Protocol -- HTTP/1.1", RFC 2616draft, June 1999. ...