Newer RFCs for HTTP/1.1 clarify that a request containing a message body must contain either a Content-Length header or a Transfer-Encoding header. Unlike response bodies, which can be terminated by closing the connection, this is not allowed for HTTP requests.

This should be reflected in the HTTPServerRequestImpl and HTTPClientSession classes.

This will also solve an issue with WebDAV clients, as the WebDAV protocol relies on correct message framing. WebDAV methods may or may not include a request body, and the presence of it is entirely defined based on the presence of a Content-Length or Transfer-Encoding header.