> Em 10 de mai. de 2021, à(s) 18:04, Willy Tarreau <w...@1wt.eu> escreveu:
>
> On Mon, May 10, 2021 at 10:41:36PM +0200, Willy Tarreau wrote:
>>> core.register_action("auth", { "http-req" }, function(txn)
>>> txn:set_var("txn.code", 401, true)
> ^^^^
> So the problem is exactly here and it works as designed. This
> argument "ifexist" was added a year ago to avoid Lua allocating
> random variable names:
>
> 4e172c93f ("MEDIUM: lua: Add `ifexist` parameter to `set_var`")
>
> What the "true" argument does here is to refrain from creating
> the variable if it does not exist. After you look it up from the
> service, the variable gets created and it exists, hence why it
> then works next times.
>
> If you want it to always be created (which I assume you want
> to), just drop this argument or explicitly set it to false.
Thanks Willy for the explanation and sorry about the false alarm, I didn’t see
the whole picture here.
Just to confirm how it works, I created the snippet below:
http-request lua.auth ## assigning txn.core
http-request return lf-string %[var(txn.code)] content-type text/plain
It worked since the first run and this is the only place I declared txn.code.
Does this mean that a var is created in the following conditions? Any change in
the sentences below?
- after the first read from a Lua script
- after the first write from a Lua script provided that ifexists parameter is
set to false
- always exists, if used anywhere in the configuration file
Thanks,
