[13.x] Allow Http Client to be used as PSR Client#60295
Merged
taylorotwell merged 3 commits intoMay 27, 2026
Conversation
86b660c to
0af4f91
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This makes some options used internally by the Http client optional so that the client returned by
buildClientcan be used anywhere that an instance of\Psr\Http\Client\ClientInterfaceis required. This allows the middleware and the handler stack to be used on all requests made using the client, which means things like request logging will also apply.For example, say your application uses a package that allows address geocoding and has different drivers available for different map providers. The service class in this package must be instantiated with an instance of
\Psr\Http\Client\ClientInterface, which it then uses to make API requests to the corresponding map providers. By passing the Laravel Http client, all requests and responses from these APIs can then be logged alongside all the other Http requests being made directly by application code.