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

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

                Author: ASF GitHub Bot
            Created on: 12/Aug/16 21:47
            Start Date: 12/Aug/16 21:47
    Worklog Time Spent: 10m 
      Work Description: GitHub user shinrich opened a pull request:

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

    TS-2987: Add new TS API TSHttpTxnPluginTagGet

    

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

    $ git pull https://github.com/shinrich/trafficserver ts-2987

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

    https://github.com/apache/trafficserver/pull/865.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 #865
    
----
commit 19ce150fc82b1a13160ca267b793f9059e500613
Author: Susan Hinrichs <shinr...@ieee.org>
Date:   2016-08-12T21:30:59Z

    TS-2987: Add new TS API TSHttpTxnPluginTagGet

----


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

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

> TS API to identify if the client connection is via HTTP/2
> ---------------------------------------------------------
>
>                 Key: TS-2987
>                 URL: https://issues.apache.org/jira/browse/TS-2987
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: HTTP/2, TS API
>            Reporter: Sudheer Vinukonda
>             Fix For: 7.0.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Need a TS API for the plugins to be able to identify whether the incoming 
> client connection is via SPDY. The plugins would like to relay this 
> information over to the origins which may return a different kind of response 
> for a spdy client vs a non-spdy client. For example, the origins may skip the 
> optimizations such as domain-sharding which work well with non-spdy clients, 
> but, would cancel the benefits of spdy to multiplex requests. 
> The proposed API (the sole credit goes to [~amc]) checks the plugin_tag to 
> identify if the connection is spdy. In the future, the HttpSM data structure 
> may be enhanced to store a spdy indicator.



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

Reply via email to