If a REST client call fails, the status code is forwarded to the client

[lorenzobenvenuti]

Describe the bug

Hi,

if a REST calls fails while serving a request, the application forwards the status code to the client (and nothing is logged on the server). Since the underlying error is caused by an unhandled exception on the server, I was expecting a 500.

It looks like the same issue was addressed in this PR, I'm wondering if there was a regression.

Thanks,

lorenzo

Expected behavior

The server returns a 500

Actual behavior

The server returns the status code of the response that caused the REST call to fail.

How to Reproduce?

GreetingResourceTest#helloEndpointReturnsA500WhenTheRestClientCallFails test in https://github.com/lorenzobenvenuti/rest-client-exception-bug

Output of uname -a or ver

No response

Output of java -version

No response

GraalVM version (if different from Java)

No response

Quarkus version or git rev

2.16.3

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

No response

[quarkus-bot]

/cc @Sgitario (rest-client), @cescoffier (rest-client), @geoand (rest-client)

[geoand]

Actually, this has been fixed in the Reactive REST Client.

If you substitute quarkus-rest-client-jackson with quarkus-rest-client-reactive-jackson, everything works as expected

[lorenzobenvenuti]

TYVM!

[geoand]

🙏