[
https://issues.apache.org/jira/browse/TS-2987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419500#comment-15419500
]
Susan Hinrichs commented on TS-2987:
------------------------------------
I think the discussion of creating an API to get information about the client
connecting protocols has moved onto TS-4703.
However, this API is still useful for plugin writers wanting to gather
information about the invoking plugin (for logging or whatever). [~sudheerv]
added this API to our version of ats-5.3.x. At least one group has used
TSHttpTxnPluginTagGet just to track information about their own plugins.
I'll go ahead and put up a PR with what we have been running with. Has this
API gone through the API review yet? If not, I'll get that kicked off.
> 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
>
>
> 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)
