You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, we are just testing regression for memoize. We should programmatically build tests for each feature flag set permutation or build tag.
Quoting our build tags from README:
coraza.disabled_operators.* - excludes the specified operator from compilation. Particularly useful if overriding the operator with plugins.RegisterOperator to reduce binary size / startup overhead.
coraza.rule.multiphase_valuation - enables evaluation of rule variables in the phases that they are ready, not only the phase the rule is defined for.
memoize_builders - enables memoization of builders for regex and aho-corasick dictionaries to reduce memory consumption in deployments that launch several coraza instances. For more context check corazawaf/coraza-caddy#76
no_fs_access - indicates that the target environment has no access to FS in order to not leverage OS' filesystem related functionality e.g. file body buffers.
coraza.rule.case_sensitive_args_keys - enables case-sensitive matching for ARGS keys, aligning Coraza behavior with RFC 3986 specification. It will be enabled by default in the next major version.
We should consider tests for each permutation of build tags.
The text was updated successfully, but these errors were encountered:
Right now, we are just testing regression for memoize. We should programmatically build tests for each feature flag set permutation or build tag.
Quoting our build tags from README:
We should consider tests for each permutation of build tags.
The text was updated successfully, but these errors were encountered: