nested access_by_lua

david.northetal · 2018-02-02T18:45:32+00:00

Hi, The raw_log API is scheduled to be shipped with the next release (but is already in the master branch of lua-resty-core, he...

nested access_by_lua

david.northetal

Hey,

I'm missing a conceptual understanding of why the following doesn't work:


location /foo {

  access_by_lua_block {
    -- ...
    ngx.log(ngx.ERR, "Foo ran")
  }

  location /foo/bar {
    access_by_lua_file bar/somefile.lua
  }

}


now when I send a request to "/foo/bar", I won't get "Foo ran" in my log, but I do when sending a request to "/foo".

To me `access_by_lua` directives clearly seemed to be able to be nested, but instead there nested `access_by_lua` directives seem to override the previous ones?

I've read the docs and did not spot something that would point into this direction.


Would really appreciate if someone can clear this up for me, maybe the docs could be extended to make this clear.

Regargs,
dnorth

rpaprocki

Hi David,

*_by_lua directives cannot be nested or inherited. The location blocks themselves can be nested, and Lua directive handlers can be placed within these blocks, but only the most significant handler definition "wins" and executes.

Trying to "inherit" Lua code definitions sounds like a nightmare anyway ;) The best thing to do if you want some sort of inheritance might be to define the parent/base code (e.g. code that should execute every time in a server{} block) in a Lua module somewhere, and have each child handler (e.g. Lua code that should only run in certain location {} blocks) call that module before executing its own logic. YMMV based on use case, design, etc.

On Fri, Feb 2, 2018 at 2:45 AM, David North <david.n...@gmail.com> wrote:

Hey,

I'm missing a conceptual understanding of why the following doesn't work:

location /foo {

access_by_lua_block {
-- ...
ngx.log(ngx.ERR, "Foo ran")
}

location /foo/bar {
access_by_lua_file bar/somefile.lua
}

}

now when I send a request to "/foo/bar", I won't get "Foo ran" in my log, but I do when sending a request to "/foo".

To me `access_by_lua` directives clearly seemed to be able to be nested, but instead there nested `access_by_lua` directives seem to override the previous ones?

I've read the docs and did not spot something that would point into this direction.

Would really appreciate if someone can clear this up for me, maybe the docs could be extended to make this clear.

Regargs,
dnorth.