Repository navigation
Make sure trace context headers are added only once - #1937
Conversation
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪💚 Flaky test reportTests succeeded. Expand to view the summary
Test stats 🧪
|
SylvainJuge
left a comment
There was a problem hiding this comment.
[minor] For HTTP headers, most (if not all) header accessors allow for ready & write operations, thus maybe we could have a helper method or a variant of propagateTraceContext that ensure that header has only a single value.
Yes, that's what I wanted to do at first, but then realized that in some cases it's not efficient to read (allocates iterator for example), so using |
…span-traceparent-fix
…span-traceparent-fix
…junit-support * upstream/master: Updated get-user-teams-membership to version 1.0.3 ensure that the socket is closed even if there is an exception from the other close (elastic#1946) Make sure trace context headers are added only once (elastic#1937) Update CHANGELOG.asciidoc Ecs reformatting more fields (elastic#1910) Use path when high-level framework method is unknown (elastic#1906) Semver parsing enhancement (elastic#1931)
…for-windows-only * upstream/master: (100 commits) [CI] Enable compatibility test matrix for unit tests (elastic#1915) Updated get-user-teams-membership to version 1.0.3 ensure that the socket is closed even if there is an exception from the other close (elastic#1946) Make sure trace context headers are added only once (elastic#1937) Update CHANGELOG.asciidoc Ecs reformatting more fields (elastic#1910) Use path when high-level framework method is unknown (elastic#1906) Semver parsing enhancement (elastic#1931) Bump version.slf4j from 1.7.31 to 1.7.32 (elastic#1933) Add description about memory pool metrics to docs (elastic#1925) updated team membership check in action Add 1.25.0 to cloudfoundry index Update CHANGELOG.asciidoc (elastic#1929) fixed community label action [maven-release-plugin] prepare for next development iteration [maven-release-plugin] prepare release v1.25.0 Prepare release 1.25.0 (elastic#1927) synchronize json schema specs (elastic#1926) added labeling of community issues and PRs added community labeler config ...
What does this PR do?
Make sure trace context headers are added only once to outgoing calls, even if the protocol supports multiple values per header (like in HTTP).
Checklist