[9.x] Allow HTTP client requests with retries to optionally throw RequestExceptions #40079
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.
Edit: Changed to master branch at suggestion of @driesvints.
This PR addresses #40055 by adding functionality to the HTTP client so that you can prevent it from throwing a
RequestException
whenretries
are configured.The problem
Presently, and as highlighted in the docs, the HTTP client does not throw exceptions when a request fails. As a result, you can make use of methods like
failed
on the response e.g.However, if you configure
retries
on the HTTP client, it will throw aRequestException
if all attempts fail.This means:
throw()
on the client.throw()->json()
.throwIf
.$response->failed()
.In addition, you have to wrap the request within a try/catch block if you want to handle the error.
The solution
The PR adds a fourth parameter
throw
to theretries
method, which allows you to control whether the HTTP client should throw an exception when the retry limit is reached.By default, this parameter is set to
true
to preserve backward compatibility.