martinhsv

So, this fix is really only relevant if someone is using ``` SecRule MULTIPART_UNMATCHED_BOUNDARY "@gt 0" ... ``` instead of ``` SecRule MULTIPART_UNMATCHED_BOUNDARY "@eq 1 ``` Right?

IMHO, there's nothing wrong with this pull request in isolation. It does fix use cases where the flag should be 0 but currently has an incorrect value of 2. And...

I had intended to close this unmerged, but now that we're into the transition period, I'll leave the final disposition to the new custodians. Much of what I'll summarize here...

Hi @PaulCharlton , Probably the single most useful thing would be to increase your log levels. SecDebugLogLevel set to 9 will show a lot more detail about what is happening...

Hi @PaulCharlton , Those are some good clues. In some ways it sounds a bit like something akin to https://github.com/bitly/oauth2_proxy/issues/442 . I.e. if no body is sent but a Content-Length...

Hello @brandonpayton , I'm not very clear on what you are proposing. But based on the title and main portion of the description, it sounds like maybe what you want...

Hello @brandonpayton , Interesting question. The nginx phase to which REQUEST_HEADERS is attached has been that way since the inception of ModSecurity-nginx, so I would want to tread cautiously here....

Hello @remort , Thanks for the detailed report. I seem to recall an earlier report of some inheritance issues between blocks, that may have been resolved by my predecessor in...

Hello @davand01 , The SecGeoLookupDb configuration item does work in ModSecurity v3. I have used it myself moderately recently with: ``` SecGeoLookupDB /usr/share/GeoIP/GeoLite2-Country.mmdb ```

Hello @davand01 , I do not see this effect when performing an nginx ```reload``` either. However, reading through this closed ticket, I'll note that I only have MaxMind installed. Per...