Home  >  Article  >  Backend Development  >  nginx about the difference between root and alias

nginx about the difference between root and alias

不言
不言Original
2018-07-07 15:48:242710browse

This article mainly introduces the difference between root and alias about nginx. It has certain reference value. Now I share it with you. Friends in need can refer to it.

Conclusion

Configuration demo:

location xxx {
    root yyy
}

The browser accesses xxx, and the actual access is yyy/xxx
The browser accesses xxx/abc.html, and the actual access is yyy/xxx/abc.html
The browser accesses xxx/ccc/abc.html, the actual access is yyy/xxx/ccc/abc.html

Conclusion: The root attribute will add the value of root (here yyy) to the access path (location)

Configuration demo:

locaiton xxx {
    # alias必须以 / 结束,否则无效
    alias yyy/ 
}

The browser accesses xxx, and the actual access is yyy
The browser accesses xxx/abc.html, and the actual access is yyy/abc.html
When the browser accesses xxx/ccc/abc.html, the actual access is yyy/ccc/abc.html

Conclusion: The alias attribute will replace the matching part of the access path (here is yyy) with the value of alias (here it is yyy) Here is xxx)

Example

nginx’s directory structure is as follows:

nginx/
    -html/
        -index.html
    -logs/
        - access.log
    -conf/
        -nginx.conf

1) This configuration can be seen at http://localhost:8086/access.log Go to nginx/logs/access.log, but don’t expect to be able to access documents in the html directory

server {
    listen       8086;
    server_name  localhost;
    location / {
        root   logs;
    }
}

2) With this configuration, access http://localhost:8086/log/access.log, and you can See nginx/logs/access.log;
Visit http://localhost:8086/, you can see nginx/html/index.html

server {
    listen       8086;
    server_name  localhost;
    location / {
        root   html;
        index  index.html index.htm;
    }
    # 配置成 location /log/ 或 location /log 都可以
    location /log/ {
        # 不能写成logs, 必须已 / 结束
        alias logs/;
        # 以下配置没用也可以,只是方便你输入 localhost:8086/log/ 后能,看到nginx/logs/目录下的所有文件
        autoindex on;
    }
}

3) With this configuration, visit http:/ /localhost:8086/logs/access.log, you can see nginx/logs/access.log;
Visit http://localhost:8086/, you can see nginx/html/index.html

server {
    listen       8086;
    server_name  localhost;
    # http://localhost:8086/ 访问的是
    # nginx/html/  (然后会自动显示 index.html 或 index.htm,如果存在这两个文件之一)
    # 啰嗦的注释: nginx/html(html是root的值)/(/是location的值)
    location / {
        root   html;
        index  index.html index.htm;
    }
    # http://localhost:8086/logs/ 访问的是
    # nginx/./logs/
    # .是root的值,logs是location的值
    # 请与第4种错误配置进行比较,深入理解root属性
    location /logs/ {
        # 写成./也可以
        root .;
    }
}

4) Wrong configuration

server {
    listen       8086;
    server_name  localhost;
    location / {
        root   html;
        index  index.html index.htm;
    }
    # 这样子配置是错的, 请与第三种配置比较一下
    # 关键点:root属性会把root的值加入到最终路径之前
    # 即: http://localhost:8086/logs/access.log访问的是:
    # nginx/logs/logs/access.log
    # 因为: nginx/logs(root的值)/logs(locaition的值)/access.log,
    location /logs/ {
        root /logs/;
    }
}

Excerpt: https://www.cnblogs.com/zhang... This paragraph:
The value specified by the root attribute is to be added to the final path. So the accessed location becomes the root value/locaiton value. And I don't want to add the accessed URI to the path. Therefore, you need to use the alias attribute, which will abandon the URI and directly access the location specified by alias

The above is the entire content of this article. I hope it will be helpful to everyone's learning. For more related content, please pay attention to the PHP Chinese website!

Related recommendations:

Method 2 of using XHProf to analyze PHP performance bottlenecks

The above is the detailed content of nginx about the difference between root and alias. For more information, please follow other related articles on the PHP Chinese website!

Statement:
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn