Changes between Version 1 and Version 2 of Ticket #808, comment 3


Ignore:
Timestamp:
10/13/15 10:03:47 (9 years ago)
Author:
LPardue@…

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #808, comment 3

    v1 v2  
    55> If you have use cases where separation between HTTP/1.1 and HTTP/2.0 over plain TCP is useful, then we may consider to add such functionality.
    66
    7 I'm not sure separation is the correct word, other server implementations I have tested with are able to offer support for HTTP/1.1 and h2c on the same plain TCP port. The selection of protocol within such servers is based on the request line, either a standard one (including Upgrade header, allowing negotiation without additional round trips) or the HTTP/2 connection preface.
     7I'm not sure separation is the correct word, other server implementations I have tested with are able to offer support for HTTP/1.1 and h2c on the same plain TCP port. The selection of protocol within such servers is based on the request line, either a standard one in HTTP/1.1 form (including Upgrade header, allowing negotiation without additional round trips) or the HTTP/2 connection preface.
    88
    99This issue has occurred due the inconsistency between defining {{{listen port_num http2 ssl}}} (which supports HTTP/1.1 and h2, with the protocol being selected via ALPN) and {{{listen port_num http2}}} (which only supports h2c via prior knowledge).