Francis, Thanks for the great help. Here is the update nginx configuration. http://pastebin.com/736sxcmK The public domain is actually an ip-address of the server. Let's called it 999.99.99.99 Since they are behind private firewall, for me to access this (at this stage), I have to SSH tunnel into the master server 999.99.99.99. In any case, I ping dev.999.99.99.99 on the master server aby x7311 - Nginx Mailing List - English
Hi all. Our machines are behind a private firewall. I have a master machine as proxy server so two machines (production and development) can be accessed publicly. So I can access production as http://public_url/app1, http://public_url/app2, http://pbulic_url/app3 and development as http://public_url/dev/app1, etc (actually, dev.public_url) would be a better option. However, with thby x7311 - Nginx Mailing List - English
Actually, I should reconsider my position on this after reading this: http://stackoverflow.com/questions/1459739/php-serverhttp-host-vs-serverserver-name-am-i-understanding-the-ma I am not sure how nginx reacts to that, but according to you Francis, you seems to be inline with Chris Shiflett that neither is safe nor insecure. They are pretty much the same thing. Under one circumstances, caby x7311 - Nginx Mailing List - English
Hi Francis, Thanks for the response. After reading the documentation, http://wiki.nginx.org/HttpCoreModule#.24host When the HOST is empty, it's responded with 400 as expected. I think the argument would come down to whether we trust the value sent by the user. In both use of $http_host and $host, I think the 3rd curl command is trying to send a custom header whose HOST value is user-by x7311 - Nginx Mailing List - English