Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
http triggered dotnet-isolated .NET 5 function receives empty body stream when Transfer-Encoding is 'chunked'
See original GitHub issueHi,
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
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Is there any status update on this? It’s a dealbreaker when upgrading functions to Runtime v4 and dotnet-isolated 😦
I ran into this issue myself using HttpClient.PutAsJsonAsync, spending a good amount of time isolating the problem. I’m running .NET 7 isolated (v4 runtime). My only options were to load the JsonContent buffer to get the ContentLength set, or switch to sending data via StringContent.
Any updates on this issue from the Functions team would be very helpful.