[
https://issues.apache.org/jira/browse/TS-4703?focusedWorklogId=26146&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-26146
]
ASF GitHub Bot logged work on TS-4703:
--------------------------------------
Author: ASF GitHub Bot
Created on: 02/Aug/16 14:43
Start Date: 02/Aug/16 14:43
Worklog Time Spent: 10m
Work Description: Github user SolidWallOfCode commented on the issue:
https://github.com/apache/trafficserver/pull/829
I have to disagree with James. Once upon a time, this worked (if any one
remember the "proto stack" thing). It was an explicit goal of the TS-3612 work
to get this capability back. It is useful in a number of situations to be able
to know what protocol the user agent is using to talk to ATS. I know I took no
small amount of heat when I broke this originally.
Issue Time Tracking
-------------------
Worklog Id: (was: 26146)
Time Spent: 2h (was: 1h 50m)
> 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: 2h
> 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)
