Proxies, policy groups, and providers
Hako 1.19.30 supports 23 proxy or network outbounds plus the DIRECT, DNS, REJECT, and REMATCH routing or control outbounds. See the protocol reference for the complete list and configuration paths.
Policy groups
Use select, url-test, fallback, or load-balance. Upstream removed the relay group type, so new configurations must not depend on it. Health-check URLs create real network requests; choose an endpoint that fits your privacy and availability requirements.
Providers
- Inline content is read directly by the core.
- File providers are restricted to product-managed safe paths.
- Hako downloads and validates HTTP providers, writes them atomically, and then gives the managed file to the core.
- tvOS can clear caches, so remote provider content must be rebuildable.
1 fields shown
| Field | Type | iOS | macOS | tvOS | Platform notes |
|---|---|---|---|---|---|
proxies | []map[string]any | Supported | Supported | Supported | Consumed by the Hako core. |
1 fields shown
| Field | Type | iOS | macOS | tvOS | Platform notes |
|---|---|---|---|---|---|
proxy-groups | []map[string]any | Supported | Supported | Supported | Consumed by the Hako core. |
2 fields shown
| Field | Type | iOS | macOS | tvOS | Platform notes |
|---|---|---|---|---|---|
proxy-providers | map[string]map[string]any | Managed / limited | Managed / limited | Managed / limited | Hako downloads, validates, and materializes remote content in a product-managed path. Hako manages this provider cache; tvOS may clear it and the app must be able to rebuild it. |
rule-providers | map[string]map[string]any | Managed / limited | Managed / limited | Managed / limited | Hako downloads, validates, and materializes remote content in a product-managed path. Hako manages this provider cache; tvOS may clear it and the app must be able to rebuild it. |