>There are some inconsistencies in the Web.config in regards to the maximum accepted length on a post.
>
>For example, to indicate that we would like to support a post up to 20 MB, we would define it like this:
>
>

><system.web>
>  <httpRuntime maxRequestLength="20480" />
></system.web>
>

>
>IIS default at 30MB. So, let's say I would like to support up to 40 MB. This would mean I would adjust the value around something like this:
>
>

><system.web>
>  <httpRuntime maxRequestLength="40000" />
></system.web>
>

>
>As IIS defaults to 30 MB, I would then need to also add this:
>
>

>  <system.webServer>
>     <security>
>      <requestFiltering>
>         <requestLimits maxAllowedContentLength="4000000000" />
>      </requestFiltering>
>   </security>
>

>
>As you can see, maxRequestLength and maxAllowedContentLength uses two different scales.
>
>Do you know why this has been done like this?

https://weblog.west-wind.com/posts/2016/apr/06/configuring-aspnet-and-iis-request-length-for-post-data

Rick notes but doesn't explain the scale inconsistency. One is IIS, the other ASP.NET. My first guess is legacy, maybe the IIS setting is older and dates from a time when a byte was more meaningful. Or maybe it's useful there to be able to specify a small number of bytes (less than 1K), which it may not be possible to do with the ASP.NET setting.