ngx.re.find and init parameter (see string.find)

aapo.talvensaari · 2014-11-20T18:46:36+00:00

Hello! On Wed, Nov 19, 2014 at 4:37 AM, fc23229 wrote: > - save a copy of that asset in the major machine > I don't know what you mean by "save...

ngx.re.find and init parameter (see string.find)

aapo.talvensaari

Hi,

I'm talking about these:

https://github.com/openresty/lua-nginx-module#ngxrefind

http://www.lua.org/manual/5.1/manual.html#pdf-string.find

To avoid unneccessary string creation (eg. recursive ngx.re.find), would it be possible to add init-argument (as in string.find) to ngx.re.find so that it could be used as a replacement for string.find? Or alternatively should there also be ngx.re.gfind?

Does it make any sense?

Regards

Aapo

aapo.talvensaari

On Thursday, 20 November 2014 12:46:35 UTC+2, Aapo Talvensaari wrote:

Hi,

I'm talking about these:
https://github.com/openresty/lua-nginx-module#ngxrefind
http://www.lua.org/manual/5.1/manual.html#pdf-string.find

To avoid unneccessary string creation (eg. recursive ngx.re.find), would it be possible to add init-argument (as in string.find) to ngx.re.find so that it could be used as a replacement for string.find? Or alternatively should there also be ngx.re.gfind?

Does it make any sense?

Okay,

I'm anwering my own question:

ctx, can be a Lua table holding an optional pos field. When the posfield in the ctx table argument is specified, ngx.re.match will start matching from that offset (starting from 1). Regardless of the presence of the pos field in the ctx table, ngx.re.match will always set this pos field to the position after the substring matched by the whole pattern in case of a successful match. When match fails, the ctx table will be left intact.