[
https://issues.apache.org/jira/browse/TS-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neil Craig updated TS-2729:
---------------------------
Comment: was deleted
(was: Hi guys
Firstly, apologies if this is the wrong place to ask.
I have ATS 5.3, compiled (with experimental plugins) from a github pull a
couple of days ago, runnning on CentOS 6.6. I'm trying to get ATS working with
h2 as a reverse proxy but every time I enable h2 via
proxy.config.http2.enabled, proxying breaks. I've tried both http and https
backends and many variants of http_ports config.
H2 is working in that the chrome/firefox indicator shows it and i can see it in
chrome:net-internals but as i say, proxying breaks. The moment i disable h2 via
proxy.config.http2.enabled INT 0, proxying works again (as does vanilla TLS).
I can't see anything in the logs which is helpful.
Any advice or a pointer to a better place to ask would be very gratefully
received.
Cheers
Neil)
> 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: Bryan Call
> Labels: review
> Fix For: 5.3.0
>
> Attachments: 0003-h2-prototype.patch, 0004-h2-prototype.patch,
> 0005-h2-prototype.patch, h2c_upgrade.patch, hpack.patch, http2-0004.patch,
> improve-mime.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]
> This would probably require support for [Link
> preload|http://w3c.github.io/preload/#interoperability-with-http-link-header]?
> * [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)
