1. Introduction

The location directive is the core configuration in the http module. It receives requests sent by users based on predefined url matching rules. According to the matching As a result, the request is forwarded to the backend server, illegal requests are directly rejected and 403, 404, 500 error processing, etc. are returned.

2. Location instruction syntax

location [=|~|~*|^~|@] /uri/ { … } or location @name { … }

3. uri matching mode

location directive is divided into two matching modes:
1> Ordinary string matching: with = Rules for starting or starting with no leading character (~)
2> Regular matching: starting with ~ or ~* indicates regular matching, ~* indicates that regular matching is not case-sensitive

4, location uri Matching rules

When nginx receives a request, it will intercept the uri part of the request and search for all uri matching patterns defined in the location directive. In the server module, multiple location instructions can be defined to match different URL requests, and the URI matching patterns of multiple different location configurations. The overall matching principle is: first match the ordinary string pattern, and then match the regular pattern. Only the uri part is recognized. For example, the request is: /test/abc/user.do?name=xxxx

After a request comes, the process of nginx matching this request is as follows:

1> First search for an exact match starting with =, such as: location = /test/abc/user.do { … }

2> Then search for ordinary matches, with the largest prefix being In principle, if there are the following two locations, the latter one will be matched
* location /test/ { … }
* location /test/abc { … }

##3> matching After reaching a common format, the search does not end, but temporarily stores the current matching results and continues to search for the regular matching pattern

4> After the first matching item is found in all regular matching pattern locations , this item will be used as the final matching result

So the regular matching item matching rules are affected by the defined order, but the ordinary matching mode will not

5> If no regular matching item is found, Then the cached result in 3 will be the final matching result

6> If no match is found, 404 will be returned

5. The difference between exact matching and fuzzy matching The difference between location =/ { … } and location / { … }:
* The former one is an exact match and only responds to / requests. All /xxx or /xxx/xxxx type requests will not be matched in the form of prefixes. It
* The latter one is that as long as the request is prefixed with /, it will be matched. Such as: /abc, /test/abc, /test/abc/aaaa

6, regular and non-regular matching

1> location ~ /test /. .jsp$ { … }: Regular matching, supporting standard regular expression syntax.

2> location ^~ / { … }: ^~ means to turn off regular matching. When this ordinary matching pattern is searched, the regular matching pattern will no longer be searched.

...
http {
  ...
  server {
    listen    80;
    server_name localhost;

    location / {
      root  html;
      index index.html index.htm;
      # deny all; 拒絕請求，返回403
      # allow all; 允許請求
    }

    location /abc {
      deny all;
    }

    location ～ /.+\.jsp$ {
      proxy_pass http://location:9090;
    }

    # 匹配所有/test路徑下的jsp文件
    location ~ /test/.+\.jsp$ {
      proxy_pass http://localhost:8080;
    }

    # 定義各類錯誤頁
    error_page 404 /404.html

    error_page  500 502 503 504 /50x.html;
    location = /50x.html {
      root  html;
    }

    # @類似于變量定義
    # error_page 403 http://blog.csdn.net; #這種定義不允許，需求利用@定義臨時變量來實現(xiàn)
    error_page 403 @page403;
    location @page403 {
      proxy_pass http://blog.csdn.net;
    } 
  }
}

The above is the detailed content of What are the Nginx Location directive URI matching rules?. For more information, please follow other related articles on the PHP Chinese website!