[
https://issues.apache.org/jira/browse/TS-2987?focusedWorklogId=26676&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-26676
]
ASF GitHub Bot logged work on TS-2987:
--------------------------------------
Author: ASF GitHub Bot
Created on: 19/Aug/16 22:30
Start Date: 19/Aug/16 22:30
Worklog Time Spent: 10m
Work Description: Github user shinrich commented on the issue:
https://github.com/apache/trafficserver/pull/865
I didn't send one out. I'm resurrecting this one. So if a review was sent
around it was quite some time back. I'll send out a new one.
Issue Time Tracking
-------------------
Worklog Id: (was: 26676)
Time Spent: 50m (was: 40m)
> 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
> Assignee: Alan M. Carroll
> Fix For: 7.0.0
>
> Time Spent: 50m
> 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)
