[HttpClient] Fix exception triggered with AsyncResponse #38378
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.
When a request is replayed with the AsyncResponse and the 2nd request failed, users get an exception even when they pass
$throw=false
.In fact, there are 2 exceptions:
symfony/src/Symfony/Component/HttpClient/Response/CommonResponseTrait.php
Lines 51 to 68 in 73ca97c
Because CommonResponseTrait::$content is null and
self::stream
yield only the LastChunk. The content is stays nullsymfony/src/Symfony/Component/HttpClient/Response/AsyncResponse.php
Lines 209 to 225 in 73ca97c
Because on the second request passthru is null, it didn't disable the the exception thrown on destruct for the wrapped response.
This