[ 
https://issues.apache.org/jira/browse/TS-4703?focusedWorklogId=26030&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-26030
 ]

ASF GitHub Bot logged work on TS-4703:
--------------------------------------

                Author: ASF GitHub Bot
            Created on: 27/Jul/16 19:50
            Start Date: 27/Jul/16 19:50
    Worklog Time Spent: 10m 
      Work Description: GitHub user petarpenkov opened a pull request:

    https://github.com/apache/trafficserver/pull/829

    TS-4703: Adds an API call to retrieve transaction protocol

    See https://issues.apache.org/jira/browse/TS-4703

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/petarpenkov/trafficserver ts-4703

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/trafficserver/pull/829.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #829
    
----
commit fa8a9ce1480485ad5cd1866e79792a7528eef73b
Author: Petar Penkov <[email protected]>
Date:   2016-07-27T19:44:30Z

    TS-4703: Adds an API call to retrieve transaction protocol

----


Issue Time Tracking
-------------------

            Worklog Id:     (was: 26030)
            Time Spent: 10m
    Remaining Estimate: 0h

> 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
>          Time Spent: 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)

Reply via email to