Ervin Hegedus

> > But this PR definitely updates the configuration, doesn't it? > > Yes, but I'm not proposing integrating this PR right now, but at some point in the future....

> > Ahh, right - then please feel free to add labels on the right side of the page (now I added `[do not merge]`), which help us to discover...

Do not approve nor merge this yet.

I think it's done, I do not want to add anything else. I removed [do not merge] label.

> Maybe for the next release, consider going the same way as CRS and dropping the changes file in favour of the auto generated changelog through GitHub releases. Thanks, we...

Hi @EsadCetiner, thanks for this detailed report. First of all, let me ask you: lines in `H` section under expected behavior part have different `unique_id`. There are 3 or 4...

Okay, thanks for confirm the behavior. > By the way, I couldn't find an open issue related to this in this repo or the nginx one. Then this is the...

Hi @MariuszMilka, I think that's a normal behavior. ModSecurity is a WAF engine: it splits the request into several parts. The decision is in hand of rule set. The expected...

Hi @MariuszMilka, is there anything we can help you? If not, could you close this issue?

Hi @AngelSamuel, sorry for the late reply. I think the problem in your solution is here: ``` SecAction "id:400020,phase:1,nolog,pass,t:none,setvar:tx.wp_rocket_counter=0" ``` Your variable will be initialized with 0 in every transactions,...