Open tszlek-equinix opened 3 years ago
@kdavisk6 Hi, 👋 can I give it a try in the scope of Hacktoberfest? Could you assign it to me?
Absolutely @gitaroktato go for it
@kdavisk6 I have two alternatives for solving the issue:
Could you take a brief look and suggest which one aligns better with the existing design? The main problem is that the root cause of the HTTP protocol error is in the thrown exception's stack trace. So it's required for someone who would like to understand what was the issue. If I use the original ErrorDecoder's interface then this information is lost, because it's receiving the response instead of the exception.
Hey @velo, is this issue closed. If not I would like to give it a try
Still needs work.
Probably some tests showing the issue and handling the exception at Client code
Hi, I have discovered issue when using
feign.httpclient.ApacheHttpClient
. In some cases Apache client throwsProtocolException
which is a checked exception. This happens for example when server returned 303 HTTP code but there was no location header. In such case Feign proxy throwsUndeclaredThrowableException
instead of invoking ErrorDecoder.