Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
I'm a long time JAX-RS client proxy user which likes the usage of interface generated clients very much. Now I wanted to give feign a try and see how it performs. Setup is simple and integrates nicely in the Spring ecosystems.
But there are still some things which are quite inconvenient and IMHO better solved in JAX-RS.
Why not just providing an option in the builder whether to throw or to ignore 302 and leaving the default as before to keep backwards compatibility?
Even If I would try to live with the exception that is thrown, how do I get access to the
I would love at least to see that exposing of the response in
I misunderstood your issue. My suggestion is to not use
The Spring Cloud documentation outlines how to use these with Spring Cloud OpenFeign
I do agree, that leaving the handling of redirects up to the
Unfortunately, that's the case right now. The
We have a number of issues open around improving