Re: Rewriting location directive by upstream servers

2014-09-30 Thread Francis Daly
On Fri, Sep 26, 2014 at 10:12:47AM +0530, thunder hill wrote: > On Fri, Sep 26, 2014 at 2:35 AM, Francis Daly wrote: > > On Fri, Sep 26, 2014 at 01:20:18AM +0530, thunder hill wrote: Hi there, > > > When I access mysite.com/app1 the upstream server rewrites the url like > > > mysite.com/login in

Re: Rewriting location directive by upstream servers

2014-09-25 Thread thunder hill
Hi, On Fri, Sep 26, 2014 at 2:35 AM, Francis Daly wrote: > On Fri, Sep 26, 2014 at 01:20:18AM +0530, thunder hill wrote: > > Hi there, > > > When I access mysite.com/app1 the upstream server rewrites the url like > > mysite.com/login instead of mysite.com/app1/login and the result is a > > blan

Re: Rewriting location directive by upstream servers

2014-09-25 Thread Francis Daly
On Fri, Sep 26, 2014 at 01:20:18AM +0530, thunder hill wrote: Hi there, > When I access mysite.com/app1 the upstream server rewrites the url like > mysite.com/login instead of mysite.com/app1/login and the result is a > blank page. > > Users are allowed either mysite.com/app1 or mysite.com/app2

Rewriting location directive by upstream servers

2014-09-25 Thread thunder hill
Hi, I have two back end application servers behind nginx. The configuration is as follows upstream backend1 { server 10.1.1.11; } upstream backend2 { server 10.2.2.2; } server { listen 80; server_name mysite.com; location /appl1 { #proxy_set_header X-Real