From 0dcc20d068f45c4b95b013d3ed600a5fc8104276 Mon Sep 17 00:00:00 2001 From: David Acker Date: Fri, 19 Aug 2022 17:15:47 -0400 Subject: [PATCH] Clarify order of precedence for size limits (#26790) --- aspnetcore/fundamentals/middleware/request-decompression.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/aspnetcore/fundamentals/middleware/request-decompression.md b/aspnetcore/fundamentals/middleware/request-decompression.md index 153a37d743..1da91d6f46 100644 --- a/aspnetcore/fundamentals/middleware/request-decompression.md +++ b/aspnetcore/fundamentals/middleware/request-decompression.md @@ -66,10 +66,10 @@ In order to guard against [zip bombs or decompression bombs](https://en.wikipedi * The maximum size of the decompressed request body is limited to the request body size limit enforced by the endpoint or server. * If the number of bytes read from the decompressed request body stream exceeds the limit, an [InvalidOperationException](xref:System.InvalidOperationException) is thrown to prevent additional bytes from being read from the stream. -The maximum request size for an endpoint is set by: +In order of precedence, the maximum request size for an endpoint is set by: -* , such as or for MVC endpoints. -* The global server size limit . `MaxRequestBodySize` can be overridden per request with , but defaults to the limit configured for the web server implementation. +1. , such as or for MVC endpoints. +2. The global server size limit . `MaxRequestBodySize` can be overridden per request with , but defaults to the limit configured for the web server implementation. | Web server implementation | `MaxRequestBodySize` configuration | | --------- | --------- |