You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "David Calavera (JIRA)" <ji...@apache.org> on 2016/11/03 15:14:59 UTC
[jira] [Created] (TS-5030) Proposal: Add API to get the client
request UUID directly from a TSHttpTx
David Calavera created TS-5030:
----------------------------------
Summary: 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
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)