Fix HTTP client config handling #35553
Merged
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.
Defining a
key
parameter in thequery
option of a scoped HTTP client triggers an error:This PR fixes this issue but an edge case still remains with YAML and PHP config. If one wants to define parameters
key=foo
,value=bar
and nothing else, the query will actually befoo=bar
instead ofkey=foo&value=bar
. Not sure how to fix this case without breaking the tests I added here.