All files from this thread

File Name	File Size		Posted by	Date
smime.p7s	6 KB	open | download	GreenGecko	03/21/2013	Read message

Thanks for your updates. We are able to proxypass to another domain. But
the issue is domain’s sub directories are not working fine.



That is in



server {

listen 80;

server_name geotest.com;

proxy_set_header Host geotest.com;

proxy_set_header X-Real-IP $remote_addr;

proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

location / {

proxy_pass http://192.168.1.1;

}

location /cms {

proxy_pass http://192.168.1.2;

}

}



While accessing geotest.com/cms we are getting the application that running
on 192.168.1.2 but when we access geotest.com/cms/address we are not
getting the address page but insated we are getting the same index page.



That’s we are unable to access any subdirectories inside /cms/ if we access
we are getting the index page only.



So can you please guys help us on it.



Thanks

Geo


On Wed, Mar 20, 2013 at 2:12 PM, Igor Sysoev <igor@sysoev.ru> wrote:

> On Mar 19, 2013, at 18:41 , Andreas Weber wrote:
>
> Im not expert but i think you must specify /cms BEFORE / because "/" will
> match everything
>
>
> No. Since "/" and "/cms" are not regex locations, nginx finds the maximum
> match despite
> location order. This is why using only non-regex locations allows to
> create at once large and
> easy to maintain configurations with a lot of locations.
>
>
> --
> Igor Sysoev
> http://nginx.com/services.html
>
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx