http triggered dotnet-isolated .NET 5 function receives empty body stream when Transfer-Encoding is 'chunked'

Hi,

we are experiencing a problem with an http triggered dotnet-isolated .NET 5 function ~~behind Azure API Management~~. When Transfer-Encoding is set to 'chunked', the `HttpRequestData.Body` stream is always empty. Is this a scenario which is expected to work out of the box?

If what I describe is expected to work, what information do you need us to provide, to investigate the cause of the experienced problem further?

**Update:** `HttpRequestData.Body` stream is also empty when calling the function directly. I updated the title to reflect this.

Thanks! David

The issue names no files, tests, or entry points. Start by reproducing a direct HTTP-triggered .NET isolated function request with Transfer-Encoding set to chunked, then inspect the HttpRequestData.Body handling; done means the request body is available through the stream or the failure is isolated with actionable diagnostics.

Written by the indexing model from the issue text.