Re: quick question

agentzh · 2012-09-04T04:10:22+00:00

Hello! On Thu, Aug 30, 2012 at 8:25 PM, Maanas wrote: > > 3. One thing is to prevent twisted and lengthy nginx.conf files. > I do not understand th...

Re: quick question

agentzh

Hello!

On Mon, Sep 3, 2012 at 6:31 AM, Tzury Bar Yochay wrote:
> what is the api to be used so if a decision was made in access_by_lua phase,
> body_filter_by_lua will be skipped.
> that is, responding in own content and avoiding the upstream capturing,
>
> assuming conf file looks like
>
> location / {
>
>             header_filter_by_lua_file   '/etc/lua-ngx/ngx_header.lua';
>             access_by_lua_file
> '/etc/lua-ngx/filter/ngx_request.lua';
>             body_filter_by_lua_file
> '/etc/lua-ngx//filter/ngx_response.lua';
>
> }

Just use ngx.exit(). For example,

    access_by_lua '
        ngx.status = 200
        ngx.say("this is my content!")
        ngx.exit(200)
    ';

    # later running phases will never be executed...

This is more efficient than abusing ngx.exec() for this purpose ;)

BTW, I'm cc'ing the openresty-en mailing list:
https://groups.google.com/group/openresty-en

Best regards,
-agentzh

agentzh

Hello!

On Mon, Sep 3, 2012 at 1:24 PM, Tzury Bar Yochay wrote:
> I tried that before switching to .exec, however, if within access_by_lua
> there is an ngx.header.XXX then it does not behave that way.
>

Ah, I see. The header and/or body filters defined by Lua in the
current location will indeed be run anyway. Internal redirects should
work here as long as you do not define Lua filters in the new location
that it jumps to :)

Best regards,
-agentzh

tzury

I tried that before switching to .exec, however, if within access_by_lua there is an ngx.header.XXX then it does not behave that way.

sent from a mobile.

On Sep 3, 2012 11:10 PM, "agentzh" <age...@gmail.com> wrote:

Hello!

On Mon, Sep 3, 2012 at 6:31 AM, Tzury Bar Yochay wrote:
> what is the api to be used so if a decision was made in access_by_lua phase,
> body_filter_by_lua will be skipped.
> that is, responding in own content and avoiding the upstream capturing,
>
> assuming conf file looks like
>
> location / {
>
> header_filter_by_lua_file '/etc/lua-ngx/ngx_header.lua';
> access_by_lua_file
> '/etc/lua-ngx/filter/ngx_request.lua';
> body_filter_by_lua_file
> '/etc/lua-ngx//filter/ngx_response.lua';
>
> }

Just use ngx.exit(). For example,

access_by_lua '
ngx.status = 200
ngx.say("this is my content!")
ngx.exit(200)
';

# later running phases will never be executed...

This is more efficient than abusing ngx.exec() for this purpose ;)

BTW, I'm cc'ing the openresty-en mailing list:
https://groups.google.com/group/openresty-en

Best regards,
-agentzh