[ https://issues.apache.org/jira/browse/TS-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14312983#comment-14312983 ]
Leif Hedstrom commented on TS-2729: ----------------------------------- Is it possible that we prefer NPN over ALPN if the clients offers both ? > Add HTTP/2 support to ATS > ------------------------- > > Key: TS-2729 > URL: https://issues.apache.org/jira/browse/TS-2729 > Project: Traffic Server > Issue Type: New Feature > Components: HTTP/2 > Reporter: Ryo Okubo > Assignee: James Peach > Labels: review > Fix For: 6.0.0 > > Attachments: 0003-h2-prototype.patch, h2c_upgrade.patch, hpack.patch, > http2-0004.patch > > > h2. Overview > Support HTTP/2 as a client side L7 protocol. This feature is implemented into > ATS core. > Now, it supports the latest HTTP/2 draft version, h2-16. > https://tools.ietf.org/html/draft-ietf-httpbis-http2-16 > h2. How to test > # Build ATS codes normally. you need neither any build option nor external > HTTP/2 library. > # Configure settings to use https. > # Add settings to records.config to use http2. > {noformat} > CONFIG proxy.config.http2.enabled INT 1 > {noformat} > # Access to ATS by HTTP/2 client. > h2. Descriptions of current attached patches. > * 0003-h2-prototype.patch > ** For experiment. Please don't merge it. It enables to interpret HTTP/2 > requests and respond for it. But now this code is unsafe and dirty. More > refactoring is required. > h2. DONE > * Fundamental HTTP/2 frame handling > * Flow control > * Some error handlings > h2. TODO > * Refactoring > * More debugging > * Write documents > * Add test tools for HPACK, HTTP/2 frames > h2. No plan > * [Server > Push|https://tools.ietf.org/html/draft-ietf-httpbis-http2-16#section-8.2] > * [Stream > Priority|https://tools.ietf.org/html/draft-ietf-httpbis-http2-16#section-5.3] > * [Alternative > Services|https://tools.ietf.org/html/draft-ietf-httpbis-alt-svc-06] -- This message was sent by Atlassian JIRA (v6.3.4#6332)