ngx_lua + proxy_next_upstream

[pigmej at gmail.com]

Yeah, I meant rewrite obviously... I would still prefer to not have even rewrite if it's possible.

I wonder why share_all_vars is not safe. Any serious consideration / example / use case ? Why it's better to copy them instead ? (What about memory footprint etc).

And I will probably send the questions to openresty group too.

Thanks for your replies.

-----Original Message-----
From: "Yichun Zhang (agentzh)" <agentzh at gmail.com>
Sender: nginx-bounces at nginx.orgDate: Tue, 24 Sep 2013 13:28:06 
To: <nginx at nginx.org>
Reply-To: nginx at nginx.org
Subject: Re: ngx_lua + proxy_next_upstream

Hello!

On Tue, Sep 24, 2013 at 2:35 AM, Jedrzej Nowak wrote:
>
> The question is how can I do NOT redirect ?

Well, "rewrite ... break" is not a redirect. It is just an internal
URI rewrite. That's all.

> I tried with @test instead of
> /test but no success. Is there any other way to do that ?
>

Named locations can only work with internal redirects. They do not
support Nginx subrequests. You can ask the Nginx team to add support
for that to the Nginx core.

>     [...]
>     ngx.var.upstream = "192.168.1.10:9999"
>     res = ngx.location.capture('/test' .. ngx.var.request_uri,
> {share_all_vars = true})
>     [...]
>

Please note that setting the "share_all_vars" to true for your
subrequests are genreally a bad idea. Because there could be really
bad side effects. In your example, all you need is to enable the
"copy_all_vars" option.

BTW, you may want to post such questions to the openresty-en mailing
list instead:

    https://groups.google.com/group/openresty-en

Best regards,
-agentzh

_______________________________________________
nginx mailing list
nginx at nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx