Thanks for your reply. Please see this:
In Proxy server we have the setup as follows:
server {
listen 80;
server_name geotest.com;
proxy_buffering on;
proxy_redirect off;
proxy_set_header Host $host;
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.0.1/; #app1
server
}
location /cms {
proxy_pass http://192.168.0.2/; #
app2 server
}
}
Now while accessing the url the result are as follows:
1. geotest.com à Working fine getting the contents of app1 server
2. geotest.com/a1 à Working fine getting the contents of app1 server
3. geotest.com/cms à Not working. Site proxypass to app2 server but
we are getting a 404 page.
4. geotest.com/cmsssss àSame as above result.
For your information the cms application running app2 server is graphite
server and you can find the nginx configuration file from the url:
http://www.frlinux.eu/?p=199 in which we use the server name as geotest.com
So can you please help us on it.
Thanks
Geo
On Tue, Mar 19, 2013 at 2:50 PM, Francis Daly <francis@daoine.org> wrote:
> On Tue, Mar 19, 2013 at 09:25:09AM +0530, Geo P.C. wrote:
>
> Hi there,
>
> > We have 3 servers with Nginx as webserver. The setup is as follows:
>
> > So in proxy server we need to setup as while accessing geotest.com and
> all
> > its subdirectories like geotest.com/* it should go to app server 1
> except
> > while accessing geotest.com/cms and its subdirectories it should go to
> app
> > server2.
> >
> > Please let us know how we can configure it.
>
> "location /cms" should have "proxy_pass" to app2, "location /" should have
> "proxy_pass" to app1. Almost exactly as you show. Except that you spell
> "cms" "ui", for some reason.
>
> > In proxy server we setup as follows but is not working:
>
> Be specific.
>
> What one request do you make that does not give the response that you
> expect? What response do you get instead?
>
> Other things: you must set the world up so that the browser actually
> gets to your proxy server when requesting geotest.com. That's outside
> of anything nginx can do.
>
> You must set things up so that nginx actually gets to your app2 server
> when...
>
> > proxy_pass http://app2.com;
>
> ...using the name app2.com. That needs a working resolver, or a configured
> upstream block. Or just use the IP address directly here.
>
> And you will *probably* want to make sure that everything on app2 knows
> that it is effectively being served below /cms, as otherwise any links
> to other resources on that server may not work as you want.
>
> (And note that "location /cms" and "location /cms/" do different things,
> and may not both be what you want.)
>
> f
> --
> Francis Daly francis@daoine.org
>
> _______________________________________________
> 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
