[ https://issues.apache.org/jira/browse/TS-4703?focusedWorklogId=26045&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-26045 ]
ASF GitHub Bot logged work on TS-4703: -------------------------------------- Author: ASF GitHub Bot Created on: 28/Jul/16 08:58 Start Date: 28/Jul/16 08:58 Worklog Time Spent: 10m Work Description: Github user masaori335 commented on the issue: https://github.com/apache/trafficserver/pull/829 That's good idea:) @petarpenkov would you add `TSHttpSsnClientProtocolGet(TSHttpSsn ssnp)` which is wrapper of `ProxyClientSession::get_protocol_string()` ? ( Session version of `TSHttpTxnClientProtocolGet(TSHttpTnx tnxp)` ) When we want to write some plugins to extend HTTP/2 (e.g. origin-frame, cache-digest), it is useful to get client protocol at session hooks. Issue Time Tracking ------------------- Worklog Id: (was: 26045) Time Spent: 1.5h (was: 1h 20m) > Adds an API call to retrieve transaction protocol > ------------------------------------------------- > > Key: TS-4703 > URL: https://issues.apache.org/jira/browse/TS-4703 > Project: Traffic Server > Issue Type: Improvement > Components: TS API > Reporter: Petar Penkov > Fix For: 7.0.0 > > Time Spent: 1.5h > Remaining Estimate: 0h > > It would be useful if there was a way to retrieve the underlying protocol for > a given transaction through the tsapi at the very least for plugin logging > purposes. This can be achieved with a very simple method since this > information is already available internally. -- This message was sent by Atlassian JIRA (v6.3.4#6332)