IIS Incomplete Data Transfer and Status Code 400

I noticed that my asp.NET aspx page (running on IIS7.5) sometimes receives POST HTTP requests, where the length of the content in the header does not match the length of Request.InputStream.Length.

Sometimes the actual length is 0, sometimes> 0, but for these requests definitely! = The estimated length in the http header. (The clients of this page use http 1.0, so it is not associated with 100 continuation status. These are not browsers.).

I thought that such an invalid request would never be processed by my asp.net page - that IIS will return 400 (or something similar) at a lower level.

This situation sounds correct for you, and if so, is there a switch that you can switch to do this check globally in asp.net so that my page does not try to process incomplete data or should it be executed manually in code?

If necessary, clients send data with ContentType = "application / text", Keep-Alive = false.

Many thanks.