Hi there

try this

http {
upstream myapp1 {
server 192.168..16.201;
server 192.168.16.202;
server 192.168.16.203;
server 192.168.16.204;
}
server {
listen 80;
location / {
proxy_pass http://myapp1/;
proxy_set_header Host $host;
#proxy_redirect https://myapp1/ http://$host/;
}
}
}

Basically "proxy_set_header Host $host;" is passing the host name as seen by nginx to the upstream servers, so any redirect originating at upstream will redirect to the same host which it was called with. without this statement upstream servers sees host name as myapp1 which nginx uses to request them.

If this one doesn't work as expected you might like to un-comment "#proxy_redirect https://myapp1 (https://myapp1/) http://$host/;" line, although in my opinion it wont be necessary.
Regards
Pratyush Kumar
http://erpratyush..me (http://erpratyush.me)
live and let live go vegan

July 9 2016 9:56 PM, "Francis Daly" wrote:On Sat, Jul 09, 2016 at 11:23:41AM -0400, bai030805 wrote:

Hi there,
Nginx IP: 192.168.16.206
Four Web Server: 192.168.16.201-204

Is there one Host: header that you can send in requests to each of the
four web servers, so that they will all return the content that you want?

If so, use that. If not, send none. That is...
location / {
proxy_pass http://myapp1 (http://myapp1);

nginx will make a request of the upstream server including "Host: myapp1".

You can change that by using "proxy_set_header Host" with your preferred
name. (Or you can use that name instead of "myapp1" here, and in the
"upstream" definition.)

Possibly

proxy_set_header Host "";

is what you want here.

Depending on what your upstream servers send, you may need more config
in nginx to get everything to work the way that you want it to.
}

}

from web brower, i use http://192.168.16.206 to access the web server. the
web brower redirect "http://192.168.16.206" to "https://myapp1 (https://myapp1)"

If there really is a switch from http to https, that suggests that
something extra is happening.

What response do you get from

curl -v -H Host:myapp1 http://192.168.16.201/

? Because that is more-or-less the request than nginx makes.

Good luck with it,

f
--
Francis Daly francis@daoine.org (mailto:francis@daoine.org)

_______________________________________________
nginx mailing list
nginx@nginx.org (mailto:nginx@nginx.org)
http://mailman.nginx.org/mailman/listinfo/nginx (http://mailman.nginx.org/mailman/listinfo/nginx)
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx