feat: support configured headers as request options #4
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.
Hello, I came around an issue with the Client Config, for our use case we need to set a
Host
header for ceph rgw different from the base_uri provided for the client constructor, while you can set headers in the config which is then parsed and should be included in the request an alternative Host header has a buggy behaviour and is replaced by the host used as base_uri.So I wonder if we could allow to set the headers in each request separately, using headers like this should avoid this bug.
The behaviour is also described in this issue in guzzle (guzzle/guzzle#1297 - marked as solved but reported as still occurring). I realise this might be an edge case but makes sense to me to use the headers config directly like this..