Fix broken line in README
This commit is contained in:
parent
95752ff0c4
commit
3ec81cd849
@ -378,7 +378,7 @@ If set to yes, the ModSecurity WAF will be enabled.
|
|||||||
You can include custom rules by adding .conf files into the /modsec-confs/ directory inside the container (i.e : through a volume).
|
You can include custom rules by adding .conf files into the /modsec-confs/ directory inside the container (i.e : through a volume).
|
||||||
|
|
||||||
`USE_MODSECURITY_CRS`
|
`USE_MODSECURITY_CRS`
|
||||||
Values: *yes* | *no*
|
Values : *yes* | *no*
|
||||||
Default value : *yes*
|
Default value : *yes*
|
||||||
If set to yes, the [OWASP ModSecurity Core Rule Set](https://coreruleset.org/) will be used. It provides generic rules to detect common web attacks.
|
If set to yes, the [OWASP ModSecurity Core Rule Set](https://coreruleset.org/) will be used. It provides generic rules to detect common web attacks.
|
||||||
You can customize the CRS (i.e. : add WordPress exclusions) by adding custom .conf files into the /modsec-crs-confs/ directory inside the container (i.e : through a volume). Files inside this directory are included before the CRS rules. If you need to tweak (i.e. : SecRuleUpdateTargetById) put .conf files inside the /modsec-confs/ which is included after the CRS rules.
|
You can customize the CRS (i.e. : add WordPress exclusions) by adding custom .conf files into the /modsec-crs-confs/ directory inside the container (i.e : through a volume). Files inside this directory are included before the CRS rules. If you need to tweak (i.e. : SecRuleUpdateTargetById) put .conf files inside the /modsec-confs/ which is included after the CRS rules.
|
||||||
|
|||||||
Loading…
x
Reference in New Issue
Block a user