We have an asp.net core 2.1 app running on .net 4.7 in azure web app service.
Recently we started getting A LOT of the following error:
Microsoft.AspNetCore.Server.Kestrel.Core.BadHttpRequestException: Reading the request body timed out due to data arriving too slowly. See MinRequestBodyDataRate.
Our app is under pretty constant heavy load (from incoming webhooks mostly). During big spikes, we tend to see more of these.
We used to run on asp.net core 2.0 / .net 4.6.1 for many months and we never saw that error before. It seems to have started happening following our recent upgrade to asp.net core 2.1 / .net 4.7.
We'd like to get to the bottom of this issue, but we are not even sure where to start. Any thoughts?
We're seeing the same issue in production, along with a related
BadHttpRequestException triggering a 400 response: "Unexpected end of request content". We have little insight into what is causing this problem, but as little as 1 request/second with a 600KB request body will trigger it. It seems to be exacerbated by unreliable client connections, such as over mobile/cellular 3G networks. We see no related spikes in CPU or memory consumption at the time when these occur.