listen directive

Igor Sysoev igor at sysoev.ru
Thu Jul 25 07:29:53 UTC 2013


On Jul 25, 2013, at 11:23 , drook wrote:

> Hi.
> 
> I've noticed that in configuratuion like
> 
> http {
>    server {
>        server_name some.domain.tld;
>        listen 1.1.1.1;
>    }
>    server {
>        server_name another.domain.tld;
>        listen 1.1.1.1;
>    }
>    server {
>        server_name one_more.domain.tld *.domain.tld;
>        listen 1.1.1.1;
>    }
>    server {
>        server_name last.domain.tld;
>        listen 80;
>    }
> }
> 
> weird thing happens: this somehow is similar to the apache directives, where
> you should use exactly the same "address:port" in "VirtualHost" clause as
> you used in "NameVirtualHost <address:port>" directive. For example if you
> used *, you should use it everywhere, otherwise namevhost won't work. I
> found that at least on 1.2.1 similar thing happens: vhost "last.domain.tld"
> may not get any requests at all, they will be served by the *.domain.tld,
> and, if removed, by the default vhost. So I changed everything to the
> "listen 80" and it resolved the situation.
> 
> Is it some bug I stepped on, or is this normal, or, may be I just see things
> that aren't there ?

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


-- 
Igor Sysoev
http://nginx.com/services.html



More information about the nginx mailing list