Specific HTTP error code FeignExceptions about feign HOT 8 CLOSED

I believe the specific error code is already available in the exception via the response object.

The current approach to more specific exceptions is for the user to configure a ErrorDecoder which allows you to massage an exception into a application-specific one. You can have these be generic (such as your proposed 4xx vs 5xx exceptions), or very specific to the particular business use case, as you see fit.

from feign.

Sounds good, I will try it out and see if I can create some documentation/examples for this.

Thanks

from feign.

thanks!

from feign.

Would https://github.com/Netflix/feign/wiki/Custom-error-handling suffice? :)
Or would you rather have all docs in the code repo?

from feign.

Fine by me if the javadocs have a link to it. I think guava uses this
approach for the *Explained wikis.

from feign.

@adriancole Do you have a plan about adding this feature to Feign ?

from feign.

I like the wiki/documentation approach. Users will have a better set of ranges that make sense to them.

I don't want to create http code range exceptions, particularly as in many cases this is nuanced and you'll need the underlying code anyway. Ex. 3xx range includes cache-related codes as well redirects. Also, many apis that feign restfulness use 500 for everything or tunnel errors through 200. In other words, we should allow folks to define application-specific exceptions.. absolutely, but I don't think that a shared set of ranged exceptions are high enough value to add to the codebase, knowing what we know.

from feign.

@adriancole Yeah I understand! There are many different ways to process HTTP status codes.
Thanks for your quick reply.

from feign.