Ervin Hegedus

Hi @tinhutins, thanks for sending this report. Before that message, have you seen any similar one like this? ``` Audit log: Failed writing (requested ... ```

> We haven’t seen any log entry like: > > `Audit log: Failed writing (requested ...)` > > in the modsec_debug.log. sorry, I forget: in the error.log? > **The situation...

> We have another Amazon Linux 2023 (aarch64) instance in a different environment (test) running the same httpd, modsecurity version and modsecurity logging configuration — and there the audit log...

Hi @JustCoding247, > **Note**: This enhancement would significantly improve the project's build system reliability and help prevent similar issues in the future. I'm ready to contribute to implementing these CI...

@JustCoding247, thanks for this awesome description. Please let me review it in details and response then. Also Cc this comment to @theseion and @fzipi - what do you think guys?

Hi @touchweb-vincent, thanks for reporting this. What I don't understand here that you wrote: > we cannot rely on REQUEST_BODY (and therefore not on **REQUEST_BODY_LENGTH** Why do you think that...

Please take a look at this rule: ``` SecRule REQUEST_BODY_LENGTH "@gt 0" \ "id:100,\ phase:2,\ deny,\ t:none,\ msg:'Request body length is %{REQUEST_BODY_LENGTH}'" ``` This work in case of `GET` request...

> Hello, > > It seems that CRS sandbox do not support HTTP/2.0 why do you think this? > ``` > curl -v --http2 "http://sandbox.coreruleset.org/" > * Trying 52.4.200.1:80... >...

> Why do you think sandbox needs HTTP/2? I can imagine that someone wants to check the rule set against `http2`, not the previous versions. Eg. find some protocol specific...

hi @canerfilibeli, > CRS 4.20 upgrade Sorry to ask, but upgrade from what? I checked 4.0.0, the rule (eg. `941100`) is almost the same, only the `!REQUEST_COOKIES:/__utm/` negated target was...