lua and uwsgi for a location

mohammad.kolahdouzan · 2012-12-07T07:49:26+00:00

Hello! On Wed, Dec 5, 2012 at 1:40 PM, Mohammad Reza Kolahdouzan wrote: > > I am trying to use lua module for nginx, but I am getting error message wh...

lua and uwsgi for a location

mohammad.kolahdouzan

Hi,

I have a nginx.conf that contains something similar to the following:

location /a {

include /etc/nginx/uwsgi_params;

uwsgi_param UWSGI_SCRIPT some_uwsgi_script;

uwsgi_pass some_socket;

}

which calls "some_uwsgi_script" for requests going to "/a". What I need to do though is to:

1. before running "some_uwsgi_script", run a lua script

2. the lua script will then either:

a) call ngx.exit(ngx.HTTP_FORBIDDEN), which makes nginx return 403 to the user

b) or finishes with a simple return (which means some_uwsgi_script should be executed)

What I was hoping would happen is that if I added something like "content_by_lua_file some_lua_script" as the very first line of the "/a" block, it would run the lua script and once the lua returns, it would run my "some_uwsgi_script", but it does not look like doing so would do the trick! Am I doing something wrong?

Any help is appreciated.

Thanks,

agentzh

Hello!

On Thu, Dec 6, 2012 at 3:49 PM, mokolah wrote:
> I have a nginx.conf that contains something similar to the following:
>
> location /a {
>             include /etc/nginx/uwsgi_params;
>             uwsgi_param UWSGI_SCRIPT some_uwsgi_script;
>             uwsgi_pass some_socket;
> }
>
> which calls "some_uwsgi_script" for requests going to "/a". What I need to
> do though is to:
> 1. before running "some_uwsgi_script", run a lua script
> 2. the lua script will then either:
>   a) call ngx.exit(ngx.HTTP_FORBIDDEN), which makes nginx return 403 to the
> user
>   b) or finishes with a simple return (which means some_uwsgi_script should
> be executed)
>
> What I was hoping would happen is that if I added something like
> "content_by_lua_file some_lua_script" as the very first line of the "/a"
> block, it would run the lua script and once the lua returns, it would run my
> "some_uwsgi_script", but it does not look like doing so would do the trick!
> Am I doing something wrong?
>

content_by_lua_file registers a content handler for the current
location, so does uwsgi_pass. But there can only be one content
handler in effect. So you should use rewrite_by_lua or access_by_lua
instead:

    http://wiki.nginx.org/HttpLuaModule#rewrite_by_lua
    http://wiki.nginx.org/HttpLuaModule#access_by_lua

You suggest you read the Nginx tutorials here for the basic ideas on
how to use multiple Nginx modules together:

    http://agentzh.org/misc/nginx/agentzh-nginx-tutorials-enuk.html

Best regards,
-agentzh

mohammad.kolahdouzan

access_by_lua is doing the trick as I intend. Thanks for the reply.

the other link you sent for ngin modules is also very useful.

Thanks,

-M

On Thursday, December 6, 2012 3:49:24 PM UTC-8, mokolah wrote:

Hi,

I have a nginx.conf that contains something similar to the following:

location /a {
include /etc/nginx/uwsgi_params;
uwsgi_param UWSGI_SCRIPT some_uwsgi_script;
uwsgi_pass some_socket;
}

which calls "some_uwsgi_script" for requests going to "/a". What I need to do though is to:
1. before running "some_uwsgi_script", run a lua script
2. the lua script will then either:
a) call ngx.exit(ngx.HTTP_FORBIDDEN), which makes nginx return 403 to the user
b) or finishes with a simple return (which means some_uwsgi_script should be executed)

What I was hoping would happen is that if I added something like "content_by_lua_file some_lua_script" as the very first line of the "/a" block, it would run the lua script and once the lua returns, it would run my "some_uwsgi_script", but it does not look like doing so would do the trick! Am I doing something wrong?

Any help is appreciated.

Thanks,