ngx.log after ngx.redirect

fitsum.teklehaimanot · 2016-02-29T19:46:42+00:00

I made a docset for OpenResty, which can be used in dash or zeal.Now you can search the api without opening a group of tabs.The docset can be downloaded from...

ngx.log after ngx.redirect

fitsum.teklehaimanot

Hi,

I was wondering if this is a bug or not.

set $x 'true';

rewrite_by_lua '

ngx.var.x = "false"

ngx.log(ngx.NOTICE, "Value of x: ", ngx.var.x)

ngx.redirect("http://redirectedurl.com", 301)

The above configuration works and I get the notice in my log.

But when I move the redirect to the first line it stops working. Why is that?

set $x 'true';

rewrite_by_lua '

ngx.redirect("http://redirectedurl.com", 301)

ngx.var.x = "false"

ngx.log(ngx.NOTICE, "Value of x: ", ngx.var.x)

hamish.forbes

The docs explain this pretty clearly: https://github.com/openresty/lua-nginx-module#ngxredirect

Note that this method call terminates the processing of the current request and that it must be called before ngx.send_headers or explicit response body outputs by either ngx.print or ngx.say.
It is recommended that a coding style that combines this method call with the return statement, i.e., return ngx.redirect(...) be adopted when this method call is used in contexts other than header_filter_by_lua to reinforce the fact that the request processing is being terminated.

On Monday, 29 February 2016 11:46:42 UTC, fitstek wrote:

Hi,

I was wondering if this is a bug or not.

set $x 'true';

rewrite_by_lua '

ngx.var.x = "false"

ngx.log(ngx.NOTICE, "Value of x: ", ngx.var.x)

ngx.redirect("http://redirectedurl.com", 301)

';

The above configuration works and I get the notice in my log.
But when I move the redirect to the first line it stops working. Why is that?
set $x 'true';
rewrite_by_lua '
ngx.redirect("http://redirectedurl.com", 301)
ngx.var.x = "false"
ngx.log(ngx.NOTICE, "Value of x: ", ngx.var.x)
';

fitsum.teklehaimanot

Thanks, must have completely skipped over that.

On 29 Feb 2016, at 14:53, Hamish Forbes <hamish...@gmail.com> wrote:

The docs explain this pretty clearly: https://github.com/openresty/lua-nginx-module#ngxredirect

Note that this method call terminates the processing of the current request and that it must be called before ngx.send_headers or explicit response body outputs by either ngx.print or ngx.say.
It is recommended that a coding style that combines this method call with the return statement, i.e., return ngx.redirect(...) be adopted when this method call is used in contexts other than header_filter_by_lua to reinforce the fact that the request processing is being terminated.

On Monday, 29 February 2016 11:46:42 UTC, fitstek wrote:
Hi,

I was wondering if this is a bug or not.

set $x 'true';
rewrite_by_lua '
ngx.var.x = "false"
ngx.log(ngx.NOTICE, "Value of x: ", ngx.var.x)
ngx.redirect("http://redirectedurl.com", 301)
';
The above configuration works and I get the notice in my log.
But when I move the redirect to the first line it stops working. Why is that?
set $x 'true';
rewrite_by_lua '
ngx.redirect("http://redirectedurl.com", 301)
ngx.var.x = "false"

ngx.log(ngx.NOTICE, "Value of x: ", ngx.var.x)

';

--
.