Getting reverse proxy to work with dynamic request routing

nguyen.d.duc · 2015-04-30T10:11:52+00:00

Hello! On Sat, Jun 13, 2015 at 8:39 AM, Abdul Hakeem wrote: > Any updates on the proposed implementation of UDP server and TCP stream > server ? >...

Getting reverse proxy to work with dynamic request routing

nguyen.d.duc

I took the "Dynamic Request Routing Based on Redis" example from openresty.org and enabled reverse proxy but haven't been able to get the reverse proxy part of it to work. Reverse proxy works fine for hard-coded uri (e.g. http://192.168.1.24:8080/mojo) but won't work when a variable is used (e.g. http://$target). Here's an example:

server {

listen 192.168.1.24:80;

server_name 192.168.1.24;

location /mojo {

set $target '';

access_by_lua '

-- code using redis to lookup dynamic target removed for simplicity, using hard-coded value here

ngx.var.target = "192.168.1.24:8080/mojo";

# reverse proxy setup

proxy_set_header X-Forwarded-Host $host;

proxy_set_header X-Forwarded-Server $host;

proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

# this works with reverse proxy

#proxy_pass http://192.168.1.24:8080/mojo;

# this does not

proxy_pass http://$target;

}

I would like to hide the internal hosts/posts from the user but reverse proxy doesn't seem to work when proxy_pass is used with a variable. When it works, user sees http://192.168.1.24/mojo. When it doesn't work, user sees http://192.168.1.24:8080/mojo. Any ideas? I'm really stuck.

david.birdsong

Try setting $target to host and port and use lua's ngx.req.set_uri for the URL path changes.

On Wed, Apr 29, 2015 at 7:11 PM, Duc Nguyen <nguye...@gmail.com> wrote:

I took the "Dynamic Request Routing Based on Redis" example from openresty.org and enabled reverse proxy but haven't been able to get the reverse proxy part of it to work. Reverse proxy works fine for hard-coded uri (e.g. http://192.168.1.24:8080/mojo) but won't work when a variable is used (e.g. http://$target). Here's an example:

server {
listen 192.168.1.24:80;
server_name 192.168.1.24;

location /mojo {
set $target '';
access_by_lua '
-- code using redis to lookup dynamic target removed for simplicity, using hard-coded value here
ngx.var.target = "192.168.1.24:8080/mojo";
';

# reverse proxy setup
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Forwarded-Server $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

# this works with reverse proxy
#proxy_pass http://192.168.1.24:8080/mojo;

# this does not
proxy_pass http://$target;
}
}

I would like to hide the internal hosts/posts from the user but reverse proxy doesn't seem to work when proxy_pass is used with a variable. When it works, user sees http://192.168.1.24/mojo. When it doesn't work, user sees http://192.168.1.24:8080/mojo. Any ideas? I'm really stuck.

.

nguyen.d.duc

Hi David, could you tell me how to set $target to host and port. I just started learning this stuff today so sorry for the stupidity.

On Wednesday, April 29, 2015 at 10:32:11 PM UTC-4, David Birdsong wrote:

Try setting $target to host and port and use lua's ngx.req.set_uri for the URL path changes.

On Wed, Apr 29, 2015 at 7:11 PM, Duc Nguyen <nguyen...@gmail.com> wrote:
I took the "Dynamic Request Routing Based on Redis" example from openresty.org and enabled reverse proxy but haven't been able to get the reverse proxy part of it to work. Reverse proxy works fine for hard-coded uri (e.g. http://192.168.1.24:8080/mojo) but won't work when a variable is used (e.g. http://$target). Here's an example:

server {
listen 192.168.1.24:80;
server_name 192.168.1.24;

location /mojo {
set $target '';
access_by_lua '
-- code using redis to lookup dynamic target removed for simplicity, using hard-coded value here
ngx.var.target = "192.168.1.24:8080/mojo";
';

# reverse proxy setup
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Forwarded-Server $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

# this works with reverse proxy
#proxy_pass http://192.168.1.24:8080/mojo;

# this does not
proxy_pass http://$target;
}
}

I would like to hide the internal hosts/posts from the user but reverse proxy doesn't seem to work when proxy_pass is used with a variable. When it works, user sees http://192.168.1.24/mojo. When it doesn't work, user sees http://192.168.1.24:8080/mojo. Any ideas? I'm really stuck.

.

david.birdsong

it's a very small modification

<snip>

set $target '';

access_by_lua '

-- code using redis to lookup dynamic target removed for simplicity, using hard-coded value here

ngx.var.target = "192.168.1.24:8080/mojo" -- (removed trailing ';')

ngx.req.set_uri("/mojo")

</snip>

note: i haven't tested this, but i recall doing something like this recently

On Wed, Apr 29, 2015 at 8:10 PM, Duc Nguyen <nguye...@gmail.com> wrote:

Hi David, could you tell me how to set $target to host and port. I just started learning this stuff today so sorry for the stupidity.

On Wednesday, April 29, 2015 at 10:32:11 PM UTC-4, David Birdsong wrote:
Try setting $target to host and port and use lua's ngx.req.set_uri for the URL path changes.

On Wed, Apr 29, 2015 at 7:11 PM, Duc Nguyen <nguyen...@gmail.com> wrote:
I took the "Dynamic Request Routing Based on Redis" example from openresty.org and enabled reverse proxy but haven't been able to get the reverse proxy part of it to work. Reverse proxy works fine for hard-coded uri (e.g. http://192.168.1.24:8080/mojo) but won't work when a variable is used (e.g. http://$target). Here's an example:

server {
listen 192.168.1.24:80;
server_name 192.168.1.24;

location /mojo {
set $target '';
access_by_lua '
-- code using redis to lookup dynamic target removed for simplicity, using hard-coded value here
ngx.var.target = "192.168.1.24:8080/mojo";
';

# reverse proxy setup
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Forwarded-Server $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

# this works with reverse proxy
#proxy_pass http://192.168.1.24:8080/mojo;

# this does not
proxy_pass http://$target;
}
}

I would like to hide the internal hosts/posts from the user but reverse proxy doesn't seem to work when proxy_pass is used with a variable. When it works, user sees http://192.168.1.24/mojo. When it doesn't work, user sees http://192.168.1.24:8080/mojo. Any ideas? I'm really stuck.

.

agentzh

Hello!

On Thu, Apr 30, 2015 at 10:11 AM, Duc Nguyen wrote:
> Reverse proxy works fine for hard-coded
> uri (e.g. http://192.168.1.24:8080/mojo) but won't work when a variable is
> used (e.g. http://$target).

What do you mean by "won't work"? What exact phenomena are you seeing?
Are you seeing any errors in your nginx error.log file?

I've tried the following standalone and minimal example based on your
sample and it works perfectly on my side:

    server {
        listen          8080;

        location = /t {
            set $target '';
            access_by_lua '
                ngx.var.target = "http://127.0.0.1:8080/mojo";
            ';
            proxy_pass $target;
        }

        location = /mojo {
            echo "hey, there";
        }
    }

And then query /t gives:

    $ curl localhost:8080/t
    hey, there

Please note that we should not specify "http://"; again in proxy_pass
above because "http://"; is already included in the $target variable
value.

BTW, if you use domain names instead of plain IP addresses in the
variable values, then you should also configure the standard
"resolver" configuration directive accordingly:

http://nginx.org/en/docs/http/ngx_http_core_module.html#resolver

Best regards,
-agentzh