fix(browser): Respect manually set sentry tracing headers in XHR requests #16184
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Analogously to #16183 for
fetch
, this PR ensures that manually setsentry-trace
andbaggage
headers in XHR requests are respected by our XHR instrumentation and not overwritten.This also fixes a bug where we'd append multiple
sentry-trace
orbaggage
values in case the header was somehow set more than once (analogously to #13907 forfetch
)Added two integration tests to demonstrate correct behaviour.
Came up in https://linear.app/getsentry/issue/FE-380/debug-trace-context-propagation-issue-from-tanstack-to-go-backend
bundle-size wise, this probably amortizes the savings from #16183 🙃