Yeah it's 1.0.2, I compiled it from source. I'll play around some more later today, thanks for the suggestions!
-- Leif > On Feb 9, 2015, at 1:04 AM, Ryo Okubo (JIRA) <[email protected]> wrote: > > > [ > https://issues.apache.org/jira/browse/TS-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14311912#comment-14311912 > ] > > Ryo Okubo commented on TS-2729: > ------------------------------- > > Hi Leif, > > Thanks for catching. I'll fix these warnings at this weekend. > > I couldn't reproduce the ALPN problem ... please make sure that openssl-1.0.2 > is installed on the client. To test ALPN, the openssl s_server command is > useful. > > {noformat} > // server (use only ALPN) > $ openssl s_server -accept 443 -key server.key -cert server.crt -alpn h2-14 > > // client > $ nghttp -v ... > // If the client can use ALPN, the openssl s_server command print "ALPN > protocols selected: h2-14" > {noformat} > > >> 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)
