[
https://issues.apache.org/jira/browse/TS-4703?focusedWorklogId=28810&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-28810
]
ASF GitHub Bot logged work on TS-4703:
--------------------------------------
Author: ASF GitHub Bot
Created on: 12/Sep/16 16:56
Start Date: 12/Sep/16 16:56
Worklog Time Spent: 10m
Work Description: Github user SolidWallOfCode commented on a diff in the
pull request:
https://github.com/apache/trafficserver/pull/1007#discussion_r78410788
--- Diff: proxy/http/HttpSM.cc ---
@@ -7940,3 +7940,50 @@ HttpSM::is_redirect_required()
}
return redirect_required;
}
+
+// Fill in the client protocols used. Return the number of entries
returned
+int
+HttpSM::populate_client_protocol(const char **result, int n) const
+{
+ int retval = 0;
+ if (n > 0) {
+ const char *proto =
HttpSM::find_proto_string(t_state.hdr_info.client_request.version_get());
+ if (proto) {
+ result[0] = proto;
+ retval = 1;
+ if (n > 1 && ua_session) {
--- End diff --
I'd use `retval` instead of the hard coded `1` just to be consistent.
Issue Time Tracking
-------------------
Worklog Id: (was: 28810)
Time Spent: 6h 50m (was: 6h 40m)
> 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: 6h 50m
> 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)
