-
Notifications
You must be signed in to change notification settings - Fork 26
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.
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
updates to CRS v4.0.0-rc2, sets equal BodyLimits in default configs #243
Changes from 2 commits
31b7247
6c34522
5af23ed
9af30a0
b05f219
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -41,11 +41,13 @@ SecRule REQUEST_HEADERS:Content-Type "^application/json" \ | |
# to the size of data, with files excluded. You want to keep that value as | ||
# low as practical. | ||
# | ||
# Running as a Wasm plugin, we expect Limit equal to MemoryLimit: it would be prevented buffering request body to files anyways. | ||
|
||
SecRequestBodyLimit 13107200 | ||
|
||
SecRequestBodyInMemoryLimit 131072 | ||
SecRequestBodyInMemoryLimit 13107200 | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is this change connected to the 1gb? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. No, it is about:
Not being able to split the request between memory and then into a file after a certain limit, for coraza-proxy-wasm the two limits should be the same |
||
|
||
SecRequestBodyNoFilesLimit 131072 | ||
# SecRequestBodyNoFilesLimit 131072 | ||
|
||
# What to do if the request body size is above our configured limit. | ||
# Keep in mind that this setting will automatically be set to ProcessPartial | ||
|
@@ -168,19 +170,11 @@ SecResponseBodyLimitAction ProcessPartial | |
|
||
# -- Filesystem configuration ------------------------------------------------ | ||
|
||
# The location where Coraza stores temporary files (for example, when | ||
# it needs to handle a file upload that is larger than the configured limit). | ||
# | ||
# This default setting is chosen due to all systems have /tmp available however, | ||
# this is less than ideal. It is recommended that you specify a location that's private. | ||
# | ||
SecTmpDir /tmp/ | ||
|
||
# The location where Coraza will keep its persistent data. This default setting | ||
# The location where Coraza will keep its persistent data. This default setting | ||
# is chosen due to all systems have /tmp available however, it | ||
# too should be updated to a place that other users can't access. | ||
# | ||
SecDataDir /tmp/ | ||
# SecDataDir /tmp/ | ||
|
||
|
||
# -- File uploads handling configuration ------------------------------------- | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think
SecRequestBodyNoFilesLimit
is not implemented Coraza side, we should at least comment it out, not letting users think that it is enforced.