From b5ccd118bd628deff9fd3e800ad217ad702e1bee Mon Sep 17 00:00:00 2001 From: martinhsv <55407942+martinhsv@users.noreply.github.com> Date: Mon, 20 Dec 2021 17:25:47 -0500 Subject: [PATCH] Updated Reference Manual (v2.x) (mediawiki) --- Reference-Manual-(v2.x).mediawiki | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Reference-Manual-(v2.x).mediawiki b/Reference-Manual-(v2.x).mediawiki index 9725132..6e86d89 100644 --- a/Reference-Manual-(v2.x).mediawiki +++ b/Reference-Manual-(v2.x).mediawiki @@ -1238,7 +1238,7 @@ When a multipart/form-data request is being processed, once the in-memory limit ; Note : libModSecurity is able to deal with request body in a file or in a buffer (chunked or not). Web servers have properties which controls whenever a request should be saved to a file or used as a buffer (e.g. client_body_buffer_size [https://nginx.org/en/docs/http/ngx_http_core_module.html#client_body_buffer_size]) . If it is a file, ModSecurity will use the file to perform the inspection. If not, the buffer will be used. == SecRequestBodyJsonDepthLimit == -'''Description:''' Configures the maximum parsing depth that allowed when parsing a JSON object. +'''Description:''' Configures the maximum parsing depth that is allowed when parsing a JSON object. '''Syntax:''' SecRequestBodyJsonDepthLimit LIMIT