You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm having a "problem" where requests that return 4xx are thrown a client exception. This library treats any error as failure of the circuit breaker, which forces the non-use of guzzle Exceptions, having to deal with the status code.
I was wondering if it makes sense to handle Guzze's RequestException with the executeCircuitBreakerOnResponse method instead of just throwing the exception and mark as failure.
The text was updated successfully, but these errors were encountered:
I'm having a "problem" where requests that return 4xx are thrown a client exception. This library treats any error as failure of the circuit breaker, which forces the non-use of guzzle Exceptions, having to deal with the status code.
I was wondering if it makes sense to handle Guzze's RequestException with the
executeCircuitBreakerOnResponse
method instead of just throwing the exception and mark as failure.The text was updated successfully, but these errors were encountered: