You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/11/03 15:16:58 UTC
[jira] [Work logged] (TS-5030) Proposal: Add API to get the client
request UUID directly from a TSHttpTx
[ https://issues.apache.org/jira/browse/TS-5030?focusedWorklogId=31534&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-31534 ]
ASF GitHub Bot logged work on TS-5030:
--------------------------------------
Author: ASF GitHub Bot
Created on: 03/Nov/16 15:16
Start Date: 03/Nov/16 15:16
Worklog Time Spent: 10m
Work Description: GitHub user calavera opened a pull request:
https://github.com/apache/trafficserver/pull/1184
TS-5030: Add API to get the unique client request uuid from a transaction.
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 is be the signature:
```
tsapi const char * TSClientRequestUuidGet(TSHttpTxn txnp);
```
Signed-off-by: David Calavera <da...@gmail.com>
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/calavera/trafficserver client_request_uuid
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/trafficserver/pull/1184.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 #1184
----
commit 4b1a284784c93888c4d426065d9a578cd201fbd4
Author: David Calavera <da...@gmail.com>
Date: 2016-11-03T15:04:42Z
TS-5030: Add API to get the unique client request uuid from a transaction.
Signed-off-by: David Calavera <da...@gmail.com>
----
Issue Time Tracking
-------------------
Worklog Id: (was: 31534)
Time Spent: 10m
Remaining Estimate: 0h
> 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: 10m
> 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)