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
A 200 OK response is not always equivalent to a successful state. Interceptors need to be able to trigger a failure state even when the request itself did not fail.
As currently implemented, interceptors can throw an exception to trigger a failure, and I think this is the approach I'd like to recommend. Regardless, the documentation needs to be updated to explicitly cover this use case.
charliekump-wf
changed the title
Address triggering a failure in an interceptor (that could then be retried).
CP-2245 Address triggering a failure in an interceptor (that could then be retried).
Jul 28, 2016
A 200 OK response is not always equivalent to a successful state. Interceptors need to be able to trigger a failure state even when the request itself did not fail.
As currently implemented, interceptors can throw an exception to trigger a failure, and I think this is the approach I'd like to recommend. Regardless, the documentation needs to be updated to explicitly cover this use case.
fyi: @jeroencranendonk-wf
The text was updated successfully, but these errors were encountered: