fix(tracing-internal): Prefer fetch
init headers over fetch
input headers
#10176
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.
When a
fetch
call is made with aRequest
object as the input/resource param (i.e. the first) and additionally provided headers in the fetch init options (the second param),browsers ignore the headers from the request object but only add the headers from the init options when making the request.
Our
fetch
instrumentation had it the other way around, preferring headers from the request object over the headers in the options, as reported in #10172 . This PR fixes this behaviour by essentially turning around the logic we previously had.fixes #10172