Welcome! Log In Create A New Profile

Advanced

Re: server name rewrite

Francis Daly
June 19, 2013 05:28PM
On Wed, Jun 19, 2013 at 09:22:11PM +0300, wishmaster wrote:

Hi there,

> From http://wiki.nginx.org/Pitfalls I use two server's {} directives for this instead if().

> But this doesn't work and first server {} directive MUST have listen directive as well.

http://nginx.org/en/docs/http/request_processing.html

A request comes to an ip:port. nginx chooses the set of best-match servers
for that ip:port. A request indicates which Host: it cares about. nginx
chooses the one matching server from that set of servers.

Which means (approximately): if you want all possible server{} blocks to
be available to match a request, they should all have the same "listen"
directives.

> So, or I am do something wrong or wiki-page doesn't clear describe this situation?

That wiki page section doesn't any "listen" directives. I imagine the
author thought that that aspect was out of scope for that document.

f
--
Francis Daly francis@daoine.org

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Subject Author Posted

server name rewrite

artem June 19, 2013 02:24PM

question about nginx/modsecurity

aweber June 19, 2013 03:06PM

Re: question about nginx/modsecurity

Rainer Duffner June 19, 2013 03:14PM

Re: question about nginx/modsecurity

aweber June 19, 2013 03:26PM

Re: server name rewrite

Francis Daly June 19, 2013 05:28PM

Re[2]: server name rewrite

artem June 20, 2013 01:02AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 206
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready