Shulou(Shulou.com)06/01 Report--

In this issue, Xiaobian will bring you about Nginx location + regular expression 301 error. The article is rich in content and analyzed and described from a professional perspective. After reading this article, I hope you can gain something.

Before configuring nginx location, I always encountered 301 error, which is puzzling. The key is that I didn't use rewrite, but I used alias, so I suspect that alias caused 301 error.

Examples are as follows:

Example of error:

index index.html

location /zzp/ {

alias /data/nginx/zzp/exact/;

}

location ~ ^/zzp/ {

alias /data/nginx/zzp/regex/;

}

Revised example:

location /zzp/ {

alias /data/nginx/zzp/exact/;

}

location ~ ^/zzp/(.*\. html)$ {

alias /data/nginx/zzp/regex/$1;

}

Analysis:

If alias is used inside a location defined with a regular expression then such regular expression should contain captures and alias should refer to these captures (0.7.40)

The above words come from nginx documentation, meaning that when nginx location is a regular expression, this regular expression should contain captures, and alias should refer to these captures, that is, the $1 part.

Further investigate why, in stackoverflow above said is caused by the internal redirection loop, but did not understand.

The above is the Nginx location + regular expression shared by everyone. If there is a similar doubt, please refer to the above analysis for understanding. If you want to know more about it, please pay attention to the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.