Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

feat: operators generation #304

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

feat: operators generation #304

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 5 additions & 4 deletions content/docs/seclang/directives.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ title: "Directives"
Description: "The following section outlines all of the Coraza directives. "
lead: "The following section outlines all of the Coraza directives. "
date: 2020-10-06T08:48:57+00:00
lastmod: "2024-02-05T09:55:41+01:00"
lastmod: "2024-02-13T12:29:33+01:00"
draft: false
images: []
menu:
Expand Down Expand Up @@ -318,7 +318,7 @@ blocking possible. The possible values are:

**Syntax:** `SecRequestBodyInMemoryLimit [LIMIT_IN_BYTES]`

**Default:** `131072 (128 KB)`
**Default:** defaults to `RequestBodyLimit`

When a `multipart/form-data` request is being processed, once the in-memory limit is reached,
the request body will start to be streamed into a temporary file on disk.
Expand All @@ -329,7 +329,7 @@ the request body will start to be streamed into a temporary file on disk.

**Syntax:** `SecRequestBodyLimit [LIMIT_IN_BYTES]`

**Default:** `134217728 (131072 KB)`
**Default:** `134217728 (128 Mib)`

Anything over the limit will be rejected with status code 413 (Request Entity Too Large).
There is a hard limit of 1 GB.
Expand All @@ -356,6 +356,7 @@ avoid OOM issues while buffering the request body prior the inspection.
Generally speaking, the default value is not small enough. For most applications, you
should be able to reduce it down to 128 KB or lower. Anything over the limit will be
rejected with status code 413 (Request Entity Too Large). There is a hard limit of 1 GB.
**Note:** not implemented yet

## SecResponseBodyAccess

Expand All @@ -377,7 +378,7 @@ configured with [`SecResponseBodyMimeType`](#secresponsebodymimetype)).

**Syntax:** `SecResponseBodyLimit [LIMIT_IN_BYTES]`

**Default:** `524288 (512 KB)`
**Default:** `524288 (512 Kib)`

Anything over this limit will be rejected with status code 500 (Internal Server Error).
This setting will not affect the responses with MIME types that are not selected for
Expand Down
Loading