[ https://issues.apache.org/jira/browse/TS-5030?focusedWorklogId=31750&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-31750 ]
ASF GitHub Bot logged work on TS-5030: -------------------------------------- Author: ASF GitHub Bot Created on: 07/Nov/16 23:16 Start Date: 07/Nov/16 23:16 Worklog Time Spent: 10m Work Description: Github user zwoop commented on the issue: https://github.com/apache/trafficserver/pull/1184 Set the tags to the right please :). Issue Time Tracking ------------------- Worklog Id: (was: 31750) Time Spent: 1h (was: 50m) > Proposal: Add API to get the client request UUID directly from a TSHttpTx > ------------------------------------------------------------------------- > > Key: TS-5030 > URL: https://issues.apache.org/jira/browse/TS-5030 > Project: Traffic Server > Issue Type: Improvement > Components: TS API > Reporter: David Calavera > Time Spent: 1h > Remaining Estimate: 0h > > The new UUID api introduced in > https://github.com/apache/trafficserver/pull/736 is great for tracing > operations and requests. However, the most useful information for plugin > developers, the unique client request id, is not exposed as an api endpoint. > People need to understand very well how TrafficServer works internally to > generate this value. By not having the API directly exposed, people need to > repeat the same code every time they want to generate this unique identifier. > I'd like to add an API enpoint to generate this identifier based in a given > http transaction for plugins to use. > This would be the signature: > tsapi const char * TSClientRequestUuidGet(TSHttpTxn txnp); -- This message was sent by Atlassian JIRA (v6.3.4#6332)