Michael Militzer

@Kami: I can confirm that your patch fixes the issue for S3. My concern would be just that there'll still be inconsistent handling of '~' character now depending on Python...

Hi José, thanks for your reply. I don't think that it is a "classic" memory leak because the memory consumption does not gradually increase over time. Rather, it is a...

Thanks for your suggestion. But we're still on haproxy v2.0.34 and not v2.9. Also, in our case it's not the haproxy process that uses 100% cpu but it's the coraza-spoa...

I'm now seeing also the following stack traces when it crashes and it seems to be always the same crash reason. So it looks like it's actually crashing inside corazawaf...

Since we're having stability issues with the current main branch (See: https://github.com/corazawaf/coraza-spoa/issues/97) I've been following this rewrite closely hoping it would get merged and fix our issues. But since merging...

> Did you check with before the fixes I pushed a couple days ago? Yes, I used the latest version available (commit [6ea3e43](https://github.com/corazawaf/coraza-spoa/commit/6ea3e439c6d9beebc9e8361f84a34cc7968bfdf1))

> Can you try with the newest master? I fixed the disconnect handling and added a memprofile flag. If the memory leak is still happening I would love to get...

> What OS are you running and what version of GO? AlmaLinux 9.4 and go1.21.13 (Red Hat 1.21.13-3.el9_4)

@woess: Thanks for your quick reply. What concerns me about swapping out the bundled JDK is that the GraalJS 24.1.1 release notes state that "GraalJS version 24.1.1 is designed for...