Nginx - location 指令(二)

location directive

bash 复制代码
location [ = | ~ | ~* | ^~ ] uri {

}

不讨论 location @name {} 形式

官方文档有如下描述:

A location can either be defined by a prefix string , or by a regular expression .

Regular expressions are specified with the preceding ~* modifier (for case-insensitive matching), or the ~ modifier (for case-sensitive matching).

To find location matching a given request,

  • nginx first checks locations defined using the prefix strings (prefix locations). Among them, the location with the longest matching prefix is selected and remembered.
  • Then regular expressions are checked, in the order of their appearance in the configuration file. The search of regular expressions terminates on the first match, and the corresponding configuration is used.
  • If no match with a regular expression is found then the configuration of the prefix location remembered earlier is used.

If the longest matching prefix location has the ^~ modifier then regular expressions are not checked.

Also, using the = modifier it is possible to define an exact match of URI and location. If an exact match is found, the search terminates.

location 指令由修饰符和匹配项组成,匹配项可以是 前缀字符串 (prefix string,也就是仅从uri的开头匹配) 或者 正则表达式(regular expression,uri全局正则匹配),共有以下五种组合

  • prefix-string
  • = prefix-string
  • ~ regular-expression 大小写敏感
  • ~* regular-expression 大小写不敏感
  • ^~ prefix-string

注意查找匹配顺序,查找和使用的优先级并不一样:

  1. 精确匹配= prefix-string,成功则停止;
  2. 匹配其他prefix strings,选中并记住所有匹配成功中的最长匹配 (longest matching prefix);如果当前最长匹配有^~修饰符,则停止;
  3. 正则匹配[~* | ~] regular expressions,顺序为在配置文件中的出现顺序,成功则停止;
  4. 使用第2步查找到的最长匹配项,否则404 Not Found。

测试

复制代码
	location / {
		return 200 '/\n';
	}

	location /images/avatars {
		return 200 '/images/avatars\n';
	}
	
	location = /images {
		return 200 '= /images\n';
	}
	
	# 注意是否是前缀匹配 **成功** 中的 **最长** 项目
	location ^~ /images {
		return 200 '^~ images\n';
	}
	
	location ~* \.(png|jpg)$ {
		return 200 '~* \.(png|jpg)\n';
	}
url location 顺序
curl localhost / 1.2(/).3.4.=>2(/).
curl localhost/x / 1.2(/).3.4.=>2(/).
curl localhost/images = /images 1.
curl localhost/images/me.jpg ^~ images 1. 2(^~ /images).
curl localhost/images/avatars /images/avatars 1.2(/images/avatars).3.4.=>2(/images/avatars).
curl localhost/images/avatars/me.jpg ~* \.(png|jpg)$ 1.2(/images/avatars).3.
curl localhost/images/xxx/me.jpg ^~ images 1.2(^~ /images).

References

相关推荐
杨了个杨89827 小时前
Keepalived + Nginx + HAProxy 高可用架构部署实战案例
java·nginx·架构
李白的天不白18 小时前
服务器地址在哪里 pwd
运维·前端·nginx
snow@li19 小时前
nginx:详解与速查表 / Nginx = 反向代理 + 负载均衡 + 静态服务器 + HTTP 缓存 / 请求分发、静态加速、上线不中断
linux·服务器·nginx
前端程序猿i1 天前
Nginx 教程:从入门到能上线
运维·nginx
明辰之林1 天前
Nginx 1.26.2 → 1.30.2 升级指南(离线环境)
nginx
小云小白2 天前
企业抗量子落地指南(一)全链路抗量子 TLS1.3 落地指南(浏览器 → Nginx → SpringBoot)
spring boot·nginx·抗量子通信
tobias.b2 天前
JumpServer4\.10\.16离线部署\+外部Nginx反向代理 解决30分钟空闲断开WebSocket超时(延长10天)
运维·websocket·nginx
衫水2 天前
Windows Server Nginx 代理企业内网 API 偶发超时处理与保活 SOP(20260608))
运维·windows·nginx
是一个Bug2 天前
Nginx 与 API Gateway:从“小区门卫”到“商场总服务台”
运维·nginx·gateway
锋行天下3 天前
中小项目高可用,真的需要K8s吗?从单机备份到企业级架构的完整思考
后端·mysql·nginx