[
https://issues.apache.org/jira/browse/TS-4703?focusedWorklogId=26036&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-26036
]
ASF GitHub Bot logged work on TS-4703:
--------------------------------------
Author: ASF GitHub Bot
Created on: 28/Jul/16 00:55
Start Date: 28/Jul/16 00:55
Worklog Time Spent: 10m
Work Description: Github user masaori335 commented on a diff in the pull
request:
https://github.com/apache/trafficserver/pull/829#discussion_r72550556
--- Diff: proxy/InkAPI.cc ---
@@ -4655,6 +4655,15 @@ TSHttpTxnClientReqGet(TSHttpTxn txnp, TSMBuffer
*bufp, TSMLoc *obj)
return TS_ERROR;
}
+const char *
+TSHttpTxnClientProtocolGet(TSHttpTxn txnp)
+{
+ sdk_assert(sdk_sanity_check_txn(txnp) == TS_SUCCESS);
+
+ HttpSM *sm = reinterpret_cast<HttpSM *>(txnp);
+ return sm->ua_session->get_protocol_string();
--- End diff --
And we can get `client_protocol` from HttpSM directly:)
Issue Time Tracking
-------------------
Worklog Id: (was: 26036)
Time Spent: 0.5h (was: 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: 0.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)
