You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 5, 2022. It is now read-only.
The exception (e.g. on bad request 400) that is thrown by the error handler (delegated call to DefaultResponseErrorHandler.handleError()) doesn't contain the response body anymore since the stream has already been consumed by handleClientErrors() before.
I guess that is the reason why there is a strange System.out.println() with the response body, so it's not completely lost.
It would be nice if the System.out could be removed and the thrown exception could contain the response entity.
For testing I used a search request without a query -> "400 :: Query parameters are missing."
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The exception (e.g. on bad request 400) that is thrown by the error handler (delegated call to DefaultResponseErrorHandler.handleError()) doesn't contain the response body anymore since the stream has already been consumed by handleClientErrors() before.
I guess that is the reason why there is a strange System.out.println() with the response body, so it's not completely lost.
It would be nice if the System.out could be removed and the thrown exception could contain the response entity.
For testing I used a search request without a query -> "400 :: Query parameters are missing."
The text was updated successfully, but these errors were encountered: