This is a bug where a non-200 response from the server is being incorrectly captured as a client (connection) error. The log detail about the malformed message body doesn't make any sense because it looks like it's saying the client couldn't connect because of a bad payload, even though the printed payload is valid JSON.
In fact, what's happening is the server is responding with say, a 500 Internal Server Error and the code that tries to display the response body is throwing an uncaught exception cause the default Task error handler (withHandler) to capture it and deal with it.
We're often seeing something like the following in the client logs.
This is a bug where a non-200 response from the server is being incorrectly captured as a client (connection) error. The log detail about the malformed message body doesn't make any sense because it looks like it's saying the client couldn't connect because of a bad payload, even though the printed payload is valid JSON.
In fact, what's happening is the server is responding with say, a 500 Internal Server Error and the code that tries to display the response body is throwing an uncaught exception cause the default
Task
error handler (withHandler
) to capture it and deal with it.