[
https://issues.apache.org/jira/browse/TS-2987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15387022#comment-15387022
]
Masaori Koshiba edited comment on TS-2987 at 7/21/16 2:20 AM:
--------------------------------------------------------------
I agree. Tracking protocols using {{plugin_tag}} is a kind of temporal hack for
SPDY and we should stop it too.
IMO, wrapping {{ProxyClientTransaction::get_protocol_string()}} might be fine.
was (Author: masaori):
I agree. Tracking protocols using {{plugin_tag}} is a kind of temporal hack for
SPDY and we should stop it too.
IMO, wrapping of {{ProxyClientTransaction::get_protocol_string()}} might be
fine.
> 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
>
> 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)
