Hi, I dont's use upstream, because the web server is added dynamically.
I must get address from the cookie or args, then NGINX will proxy from
this address to the client browser.
I find that if I remove some security configuration in "web.xml" file of
my project like below,
CLIENT-CERT
C
Hello!
On Fri, Jun 20, 2014 at 10:14:54AM -0700, Mark Moseley wrote:
> On Fri, Jun 20, 2014 at 5:20 AM, Maxim Dounin wrote:
>
> > Hello!
> >
> > On Fri, Jun 20, 2014 at 10:51:38AM +0200, Yifeng Wang wrote:
> >
> > > Hi, It's my first time using NGINX to proxy other web servers. I set a
> > > va
On Fri, Jun 20, 2014 at 5:20 AM, Maxim Dounin wrote:
> Hello!
>
> On Fri, Jun 20, 2014 at 10:51:38AM +0200, Yifeng Wang wrote:
>
> > Hi, It's my first time using NGINX to proxy other web servers. I set a
> > variable in location, this variable may be gotten in cookie or args. if
> > I use it dire
Hello!
On Fri, Jun 20, 2014 at 10:51:38AM +0200, Yifeng Wang wrote:
> Hi, It's my first time using NGINX to proxy other web servers. I set a
> variable in location, this variable may be gotten in cookie or args. if
> I use it directly likes "proxy_pass https://$nodeIp2;";, it will get the
> respo
Hi, It's my first time using NGINX to proxy other web servers. I set a
variable in location, this variable may be gotten in cookie or args. if
I use it directly likes "proxy_pass https://$nodeIp2;";, it will get the
response for a long time. but if I hardcode likes "proxy_pass
https://147.128.22.15
