Fix: sending JSON or multipart requests #995
Open
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.
Sending url-encoded params, json or multipart requests with Guzzle is easy, because shortcuts are implemented within
GuzzleHttp\Client::applyOptions()
.Currently, those shortcuts are unreachable through the League OAuth2 Client, and thus all its providers.
This fix relies on
AbstractProvider::getResponse()
, and does not affectAbstractProvider::getAuthenticatedRequest()
.GuzzleHttp\ClientInterface::send()
method supports a second optional$options
parameter since v6.0.Upgrading
AbstractProvider::getResponse()
to support this second optional parameter allows the developper to use a"form_params"
,"json"
or"multipart"
option key :See also
Fixes: #935 #985
Duplicates: #967
For immediate use
Run the following on composer CLI:
composer config repositories.oauth2-client vcs https://github.com/fverry/oauth2-client composer require "league/oauth2-client:dev-httpclientinterface-send-options as 2.x-dev"
Workaround
Use:
Instead of: