Update clientWithDefaultUserAgent to clientWithDefaultHeaders (and defaults don't override) #1128
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.
Follow-on from #1127 that generalises the
clientWithDefaultUserAgent
to enable specifying default headers.This is so we can also store the
Authorization
header that we'll grab duringInitNetClient
. Also fixed (and tested) so that the defaults don't override the request headers.Ref: #1110