Site should not be accessed through IP

[Daniel Mostertman]

If you're using a 1-config-per-site setup, then yes, you could. It
completely depends on your setup as to where you need to place it.

You can put it in any existing file that already has a server directive in
there. Just make sure none of the other server configs/files have the
default_server in their listen directive.

The server name of _ just makes sure it won't conflict with any existing
name as hostnames are not allowed to have underscores in them.

The default_server is special, it makes sure that any request that does not
have a matching name in the rest of the config will end up there. So not
just the IP that you asked for, but also any other website name that is not
in the config.

The 444 status code is just to return a "no response" kinda thing. If you
want you can even have a default site there, telling users there is no site
at that address with a fancy text and/or logo instead.
On Apr 9, 2015 8:30 PM, "blason" <nginx-forum at nginx.us> wrote:

> Hi Finalx,
>
> you mean shall I create the .conf file by name default_server and add up
> this there? Or would you please tell me where shoudl I add the above
> stanza?
> Sorry I am being novice in nginx just would like to know more information
> about this.
>
> Posted at Nginx Forum:
> http://forum.nginx.org/read.php?2,257927,257930#msg-257930
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20150409/f0762cac/attachment.html>