[
https://issues.apache.org/jira/browse/TS-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14312514#comment-14312514
]
Leif Hedstrom commented on TS-2729:
-----------------------------------
Yeah, trying your s_server, it negotiates fine:
{code}
[root@qa1 trafficserver]# /opt/openssl/bin/openssl s_server -accept 666 -key
trafficserver.key -cert trafficserver.crt -alpn h2-14
Using default temp DH parameters
ACCEPT
ALPN protocols advertised by the client: h2-16, h2-14
ALPN protocols selected: h2-14
{code}
But my Chrome Canary does not want to talk H2 to
https://docs.trafficserver.apache.org/ . Maybe you can test it too ?
Btw, one more compiler warning to deal with:
{code}
HPACK.cc: In function ‘int64_t decode_indexed_header_field(MIMEFieldWrapper&,
const uint8_t*, const uint8_t*, Http2DynamicTable&)’:
HPACK.cc:559:68: warning: comparison between signed and unsigned integer
expressions [-Wsign-compare]
if (dynamic_table.get_header_from_indexing_tables(index, header) ==
HPACK_ERROR_COMPRESSION_ERROR) {
^
{code}
> 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)
