[ https://issues.apache.org/jira/browse/TS-2987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15387164#comment-15387164 ]
James Peach commented on TS-2987: --------------------------------- If you look in the git history we used to have a "protocol stack" object that contained a bit mask of all the protocol layers beneath a HTTP transaction. Not sure we would resurrect that code, but the concept may still be useful. It would let you express that this requests is HTTP/2 over TCP or HTTP/2 over QUIC or HTTP/1 over TLS. > 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)