You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Sebastian Pesman (JIRA)" <ji...@apache.org> on 2015/05/20 09:30:00 UTC

[jira] [Commented] (TS-3620) Should we eliminate proxy.config.http2.enabled ?

    [ https://issues.apache.org/jira/browse/TS-3620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14551938#comment-14551938 ] 

Sebastian Pesman commented on TS-3620:
--------------------------------------

I think that's safe, the browser needs to tell ATS aswell that it supports HTTP/2 which covers older browsers.

Though it forces people to use port 443, while they might want to use another port. With IPv4 maybe another program listens on 443 and you want ATS to listen on another port. With IPv6 you could easely add another public IP to the server and use the default (443) port.

> Should we eliminate proxy.config.http2.enabled ?
> ------------------------------------------------
>
>                 Key: TS-3620
>                 URL: https://issues.apache.org/jira/browse/TS-3620
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: HTTP/2
>            Reporter: Leif Hedstrom
>             Fix For: 6.0.0
>
>
> I think the consensus is that this should get controlled via normal server_ports configuration. For 6.0.0, we'll make HTTP/2 "default" I'd imagine if we have compiled in support for ALPN, and the TLS port is enabled.
> Someone would then just specify in server_ports to disable "h2", right ?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)