[
https://issues.apache.org/jira/browse/TS-4703?focusedWorklogId=28813&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-28813
]
ASF GitHub Bot logged work on TS-4703:
--------------------------------------
Author: ASF GitHub Bot
Created on: 12/Sep/16 16:59
Start Date: 12/Sep/16 16:59
Worklog Time Spent: 10m
Work Description: Github user jpeach commented on a diff in the pull
request:
https://github.com/apache/trafficserver/pull/1007#discussion_r78411137
--- Diff: proxy/api/ts/ts.h ---
@@ -2419,6 +2419,16 @@ tsapi const TSUuid TSProcessUuidGet(void);
*/
tsapi const char *TSHttpTxnPluginTagGet(TSHttpTxn txnp);
+/*
+ * Return information about the client protocols
+ */
+tsapi TSReturnCode TSHttpTxnClientProtocolStackGet(TSHttpTxn txnp, int n,
char const **result, int *actual);
+tsapi TSReturnCode TSHttpSsnClientProtocolStackGet(TSHttpSsn ssnp, int n,
char const **result, int *actual);
+tsapi int TSHttpTxnClientProtocolStackContains(TSHttpTxn txnp, char const
*tag, char const **ret_tag);
+tsapi int TSHttpSsnClientProtocolStackContains(TSHttpSsn ssnp, char const
*tag, char const **ret_tag);
+tsapi char const *TSNormalizedProtocolTag(char const *tag);
+tsapi char const *TSRegisterProtocolTag(char const *tag);
--- End diff --
Can we please be consistent about ``const char`` and ``char const``? Let's
choose one or the other and file a separate Jira to make the API consistent.
Issue Time Tracking
-------------------
Worklog Id: (was: 28813)
Time Spent: 7h 10m (was: 7h)
> 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
> Assignee: Susan Hinrichs
> Fix For: 7.0.0
>
> Time Spent: 7h 10m
> 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)
