September 13, 2010 03:34PM
On Mon, Sep 13, 2010 at 10:19:34PM +0300, Gena Makhomed wrote:

> On 13.09.2010 21:53, Igor Sysoev wrote:
>
> > Please read this:
> > http://nginx.org/en/docs/http/server_names.html#miscellaneous_names
>
> but "server_name _;" directive is no more required
> in catch-all server for nignx version 0.8.48 and newer.
>
> ======================================================================
>
> In catch-all server examples you may see the strange name “_”:
>
> server {
> listen 80 default_server;
> server_name _;
> return 444;
> }
>
> There is nothing special about this name, it is just one of a myriad of
> invalid domain names which never intersect with any real name. You may
> also use something like “--”, “!@#”, and so on.
>
> ======================================================================
>
> and nginx users should not use hack "server_name _;" in 0.8.48+ (?)
> probably this documentation fragment is slightly out-of-date ?

It probably requires some rewording, but I think if a reader reads from
the start of "Miscellaneous names" section, he should understands "_" usage.
An empty name may be a good server name, which should not handled by
default server.


--
Igor Sysoev
http://sysoev.ru/en/

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

server_name behaviour

Ensiferous September 13, 2010 02:47PM

Re: server_name behaviour

Igor Sysoev September 13, 2010 03:00PM

Re: server_name behaviour

Ensiferous September 13, 2010 03:13PM

Re: server_name behaviour

Gena Makhomed September 13, 2010 03:26PM

Re: server_name behaviour

Igor Sysoev September 13, 2010 03:34PM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 162
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 500 on July 15, 2024
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready