-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Custom ErrorDecoder and RetryableExceptions #703
Comments
I suspect that the |
Sorry forgot to mention I use
|
That is a special I suggest that you check with them first and see if there is something you can audit or update in your Spring configuration first. |
Thanks, I will investigate from the Spring side of things :) |
@Squiry Nice catch :) Any suggestions? |
Well ErrorDecoder should decode erros and there's nothing to decode anyway. |
Yeah at the moment I'm just handling RetryableException. I guess I'll stay like this. Thanks though ! |
The current implementation treats all |
Closing based on the last comment. |
thanks |
I have set up a custom ErrorDecoder which is used for all 4xx responses, but for example if the inbound server is down, my custom ErrorDecoder is never used, and instead just a RetryableException is thrown.
Is there something else I could override that will control what exception is thrown regardless of the scenario ?
Also something like this would help to create better logs... Now the logs are inconsistent because of this conditionality.
The text was updated successfully, but these errors were encountered: