Nginx - minimal configuration

# Secure servers are only allowed the required number of servers. Ideally, we would build the server based on a minimal system by enabling other features individually. Minimal configuration also helps with debugging. If the bug is not available in a minimal system, add the functionality individually and continue searching for the bug.

This is the minimum configuration required to run nginx:

# /etc/nginx/nginx.confevents {}         # event context have to be defined to consider config validhttp { server {    listen 80;    server_name  javatpoint.co  www.javatpoint.co  *.javatpoint.co;    return 200 "Hello";  }

Root, Location and try_files directives

Root directive

root directive is used Sets the root directory for requests, allowing nginx to map incoming requests onto the file system.

server {  listen 80;  server_name javatpoint.co;  root /var/www/javatpoint.co;}

It allows nginx to return server content based on the request:

javatpoint.co:80/index.html     # returns /var/www/learnfk.com/index.htmljavatpoint.co:80/foo/index.html # returns /var/www/learnfk.com/foo/index.html

Location directive

The location directive is used to set the configuration based on the requested URI (Uniform Resource Identifier).

The syntax is:

location [modifier] path

Example:

location /foo {  # ...}

If no modifier is specified, the path is treated as a prefix and anything can follow. The above example will match:

/foo/fooo/foo123/foo/bar/index.html...

We can also use multiple location directives in a given context:

server {  listen 80;  server_name javatpoint.co;  root /var/www/javatpoint.co;  location/{    return 200 "root";  }  location /foo {    return 200 "foo";  }}javatpoint.co:80  /      # => "root"javatpoint.co:80   /foo    # => "foo"javatpoint.co:80   /foo123 # => "foo"javatpoint.co:80   /bar    # => "root"

Nginx also provides some modifiers that can be used in conjunction with the location directive.

Search the public account Linux Chinese community backend and reply "private kitchen" to get a surprise gift package.

Modifiers assigned priority:

=           - Exact match^~          - Preferential match~ && ~*     - Regex matchno modifier - Prefix match

First, nginx will check for all exact matches. If it doesn't exist, it will look for the preferred option. If this match also fails, regular expression matches will be tested in the order in which they appear. If all else fails, the last prefix match will be used.

location /match {  return 200 'Prefix match: will match everything that starting with /match';}location ~* /match[0-9] {  return 200 'Case insensitive regex match';}location ~ /MATCH[0-9] {  return 200 'Case sensitive regex match';}location ^~ /match0 {  return 200 'Preferential match';}location = /match {  return 200 'Exact match';}/match     # => 'Exact match'/match0    # => 'Preferential match'/match1    # => 'Case insensitive regex match'/MATCH1    # => 'Case sensitive regex match'/match-abc # => 'Prefix match: matches everything that starting with /match'

try_files directive

This directive tries different paths and returns any found.

try_files $uri index.html =404;

Therefore, /foo.html will try to return the files in the following order:

$uri(/foo.html);index.html

If not found: 404

如果我们在服务器上下文中定义try_files，然后定义查找所有请求的位置，则不会执行try_files。发生这种情况是因为服务器上下文中的try_files定义了其伪位置，该伪位置是可能的最低特定位置。因此，定义location/ 会比我们的伪位置更具体。

server {  try_files $uri /index.html =404;  location/{  }}

因此，我们应该避免在服务器上下文中使用try_files:

server {  location/{    try_files $uri /index.html =404;  }}