Support for building with nginx configured with PCRE2#260
Support for building with nginx configured with PCRE2#260martinhsv merged 1 commit intoowasp-modsecurity:masterfrom
Conversation
Related changes in upstream: nginx/nginx@c6fec0b nginx/nginx@931acbf
|
Unfortunately, it doesn't work well when the connector module is built with PCRE2, nginx is built with PCRE2, and libmodsecurity is built with PCRE1: Full error log here: https://gist.github.com/defanator/de14eacd93eeb44a82c608d624702b85 Perhaps better option for now would be to continue building ModSecurity-nginx with PCRE1. It won't work in long-term however as PCRE1 is basically not supported anymore and eventually everything (including libmodsecurity) hopefully will migrate to PCRE2. I'll leave this one open just in case if anyone would suggest other options. |
|
Surprisingly, there are memory leaks when connector is built with PCRE1 and nginx is built with PCRE2: Full error log: https://gist.github.com/defanator/274356c4f0594331e9d128af898182ae JFTR, here are the versions of all involved components: ModSecurity-nginx: 2497e6a The environment was built from https://github.com/defanator/modsecurity-performance (Ubuntu 20.04 "focal", vagrant box UPDATE: finally, leaks are still there with module built with PCRE1 and nginx built with PCRE1, so something bad is definitely happening in connector + libmodsec combo. Also, the above numbers were gathered without any external load between nginx reloads. If e.g. |
Related changes in upstream:
nginx/nginx@c6fec0b
nginx/nginx@931acbf
This is going to be a part of upcoming nginx/1.21.5 release scheduled for December 28, 2021.