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

ASF GitHub Bot logged work on TS-3620:
--------------------------------------

                Author: ASF GitHub Bot
            Created on: 26/Jul/16 14:15
            Start Date: 26/Jul/16 14:15
    Worklog Time Spent: 10m 
      Work Description: GitHub user bryancall opened a pull request:

    https://github.com/apache/trafficserver/pull/826

    TS-3620: Enable HTTP/2 by default

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/bryancall/trafficserver TS-3620

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/trafficserver/pull/826.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #826
    
----
commit ead21d218f62695b520d779007c058edb289ebb6
Author: Bryan Call <[email protected]>
Date:   2016-07-26T14:14:22Z

    TS-3620: Enable HTTP/2 by default

----


Issue Time Tracking
-------------------

            Worklog Id:     (was: 26007)
            Time Spent: 10m
    Remaining Estimate: 0h

> Enable HTTP/2 by default
> ------------------------
>
>                 Key: TS-3620
>                 URL: https://issues.apache.org/jira/browse/TS-3620
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: HTTP/2
>            Reporter: Leif Hedstrom
>            Assignee: Bryan Call
>             Fix For: 7.0.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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)

Reply via email to