Ensure body is sent when DELETE and Transfer-Encoding

[violetagg]

According to the spec https://www.rfc-editor.org/rfc/rfc9110.html#name-delete

A client SHOULD NOT generate content in a DELETE request unless it is made
directly to an origin server that has previously indicated, in or out of band, that
such a request has a purpose and will be adequately supported.

When a user sends DELETE with content this means there is an indication that the server supports this type of requests.

[bachah]

Hi @violetagg ,

The side-effect of that change is that now the reactive webClient adds by default the 'transfer-encoding: chunked' on DELETE even when there's no body sent.

Here's a quick inline test example:
WebClient.builder().build().method(DELETE).uri(full-delete-uri).retrieve().bodyToMono(Void.class)

This forces a workaround to add 'content-length: 0' to avoid errors from the server. Was this regression taken into consideration during the change?
Since it's not backward compatible and it's not a general practice to have a body in the DELETE, why was that change done?

Thanks!

[violetagg]

@bachah Please open a new issue in order to track this regression. Thanks