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

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

                Author: ASF GitHub Bot
            Created on: 12/Sep/16 16:20
            Start Date: 12/Sep/16 16:20
    Worklog Time Spent: 10m 
      Work Description: Github user jpeach commented on the issue:

    https://github.com/apache/trafficserver/pull/1007
  
    ```
    Making all in example
    ...
    make[1]: *** No rule to make target `protocol-stack/protocol-stack.c', 
needed by `protocol-stack/protocol-stack.lo'.  Stop.
    make[1]: *** Waiting for unfinished jobs....
    ```


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

    Worklog Id:     (was: 28788)
    Time Spent: 4h 40m  (was: 4.5h)

> 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: 4h 40m
>  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