Matching conditions
Routing rule
Routing rules direct connections that have entered the core to an outbound based on conditions such as domain, destination address, or port. Rule order and the handling of unmatched traffic both affect the outcome. When checking routing, first confirm which rule set is actually enabled.
Outbound selection
Traffic routing
Traffic routing lets rules determine whether each connection goes direct, through a proxy, or is blocked. Setting a domain to direct only affects connections that match that rule. Images, APIs, and other domains on the same page may each match different rules.
IP range data
GeoIP
In routing, GeoIP usually refers to IP range data grouped by geographic region or another category, used to match destination IPs. It does not measure a server's physical location in real time. Matching depends on whether the core has the IP address and whether the data file covers that range.
Domain rule data
GeoSite
GeoSite is categorized domain rule data that a core can reference to match domains. Unlike GeoIP, which matches IP ranges, GeoSite matches domains. Category names do not guarantee fixed contents; check the data version in use to determine what it covers.
App proxy entry point
System proxy
A system proxy is an operating system setting that provides proxy access to apps. “Set system proxy” configures that access for apps that honor the setting. It does not determine which outbound handles traffic after it enters the core. If an app ignores the system proxy, changing routing alone will not send its connections through the core.