The issue occurs when a client request to a cluster node is replicated to other nodes for verification, and the Content-Length is forwarded. Specifically, on a DELETE request, the body is ignored, but if the initial request had a Content-Length value other than 0, the receiving nodes would wait for the body and eventually timeout.