To clarify, I am NOT using regexp as a replacement for locations. Some of the
things that I need to do might be possible with locations. Most aren’t. I have
to test more than just the request_uri and logically I have to use AND/OR and
nested conditions. So it’s largely unfeasible with core Nginx
On 9/26/23 8:30 AM, Lance Dockins wrote:
Up until now, I had assumed that string.match types of statements were
just transparently calling PCRE behind the scenes so that the
associated memory from the PCRE call was being freed after use. Maybe
that’s not even an accurate read on how Nginx is
Dmitry,
I’ve been testing this more and I think that there’s more going on here than I
was originally thinking. I have some js_set code that I have to run to properly
route and filter requests and I noticed that it was consuming around 1mb per
request (which woudl then carry to later header fil
