Rule keywords
Rule
A Rule describes what to do when a condition is met. In a list checked in order, the first valid match usually determines where a request goes, so consider placement carefully for more specific rules. After adding a rule, verify that it matches as intended; its presence in a file alone does not prove it is active.
Rule keywords
DOMAIN-SUFFIX
DOMAIN-SUFFIX matches a domain suffix. For example, example.com can match that domain and its subdomains. It matches domains, not URL paths or query parameters. Check the scope to avoid a broad suffix rule matching a subdomain that needs separate handling.
Rule keywords
DOMAIN / DOMAIN-KEYWORD
DOMAIN matches an exact domain, while DOMAIN-KEYWORD checks whether a domain contains a specified keyword. The latter has a broader scope and may match similarly named domains with different purposes. If you only need to handle one host, understand the boundaries of exact matching; do not use a keyword rule as a suffix rule.
Rule keywords
GEOIP
GEOIP uses an IP geolocation database to determine an address's location. For example, GEOIP,CN,DIRECT sends matching addresses to DIRECT. Database results do not indicate a company's place of registration or the user's physical location. Both DNS results and database contents can affect the match; if it seems wrong, check the destination IP.
Rule keywords
IP-CIDR / IP-CIDR6
IP-CIDR matches IPv4 address ranges; IP-CIDR6 matches IPv6 address ranges. The number after the slash is the network prefix length. These rules match IP ranges, not domain text. A service may use multiple addresses or both IPv4 and IPv6, so one range may not cover every connection.
Rule keywords
FINAL
FINAL handles requests that did not match any earlier rule and is usually placed at the end of the list. It determines what happens to the remaining requests; it does not match a specific domain. Before changing FINAL, check that the existing action works and understand which requests are not covered. Do not stop after testing only a few websites.
Rule keywords
PROXY / DIRECT / REJECT
These uppercase terms are rule actions: PROXY sends requests through a proxy, DIRECT connects directly, and REJECT blocks the request. They are distinct from the Proxy and Direct interface terms in Global Routing. DIRECT does not mean the client stops processing the request; consider the current configuration, including DNS and routing behavior.
Rule keywords
USER-AGENT
USER-AGENT matches recognizable User-Agent information in requests. This information is not visible in every connection and is not a reliable substitute for app identification; one app may also make different kinds of requests. Visibility into encrypted requests depends on the circumstances, so do not assume this rule identifies all app traffic.