What is the best practice of HTTP header propagation?

Our team wants to use Istio’s content-based routing and wonders how to neatly propagate the “contents” needed for routing in our code. (For example, ‘end-user’ HTTP header in bookinfo example.)

In my guess, it could be done by something similar to propagating the headers needed for OpenTracing.

We use HTTP for all requests and our services will be written in Java or Node.

Thanks in advance for your answers :slight_smile:

@Sanha_Lee I don’t have a best practice but since you haven’t gotten any responses, I’ll point out a few links which may be of use.

@ericvn Thanks for your kind response!
As far as I have researched, OpenCensus seems to be the best fit in my case.
I found it out in this toy example.
If you or someone else knows some other stuffs, please let me know.

Thanks again!