jersey-netty-connector: response body not processed when content-length/transfer-encoding headers are not present

[sxsubram]

Invocation of a rest endpoint returns a response that does not contain content-length or transfer-encoding headers but has connection: close header set. When we read the response entity the inputstream has 0 bytes causing a downstream processing error.

From https://www.rfc-editor.org/rfc/rfc9112#name-message-body-length
this is a response message without a declared message body length, so the message body length is determined by the number of octets received prior to the server closing the connection.

jersey-netty-connector should return a body in this case.