Calling Response#getResponseBodyAsByteBuffer will return a new ByteBuffer but the current position will be the end of the buffer, rather than the start, causing to rewind manually the buffer.
The allocated byte buffer should have the position set to zero.

Problematic code is found at NettyResponse#getResponseBodyAsByteBuffer.

Just a side note: previous client returned the byte buffer with position zero.