docs: explain domain rule precedence

This commit is contained in:
Xiaoguang Sun 2026-09-27 04:28:30 +00:00
parent 19608dd2ef
commit f138e9efcb

View File

@ -95,6 +95,9 @@ cidr=192.168.100.0/24
include=office.list.example include=office.list.example
``` ```
When a destination matches domain rules in multiple rule groups, Glider uses the most specific matching domain (the longest matching domain suffix). For example, a rule for `service.example.com` takes precedence over a rule for `example.com` for requests to `service.example.com` and its subdomains, regardless of the order in which those rule files are loaded. Other subdomains of `example.com` continue to match the broader rule.
See: See:
- [office.rule.example](rules.d/office.rule.example) - [office.rule.example](rules.d/office.rule.example)
- [examples](examples) - [examples](examples)