Additional headers
The letakof-* response headers a provider can add to restrict settings, Whitelist mode and the full configuration view.
A provider can add letakof-* headers to the subscription response to limit parts of the app. Nothing is limited by default. A header restricts only when its value is disable (also disabled, 0, false, no, off, deny, in any case). No header, or any other value, allows everything.
letakof-edit-settings: disable
letakof-wifi-whitelist: disable
letakof-view-config: disable
| Header | Purpose | Default | Platforms |
|---|---|---|---|
letakof-edit-settings |
Connection settings and custom rules open read-only. GEO databases can still be downloaded. | Allowed | iPhone, Android |
letakof-wifi-whitelist |
Whitelist mode is unavailable on Wi-Fi and Rules is used instead. On mobile data your chosen mode returns. Applies to manual choice and to network scenarios. | Allowed | Android phones and iPhone (need letakof-wl) |
letakof-view-config |
Hides the Full configuration page. | Allowed | Windows, macOS, iPhone, Android |
letakof-wl: enable |
Turns on Whitelist mode (called Allowlist on iPhone) and its Allowed domains and Allowed IP addresses lists. The only value that enables something; without it the mode is hidden. | Off | Android phones, iPhone |
On platforms not listed, the header is ignored; for example, Whitelist mode does not exist on Windows and macOS.
Good to know
- The policy comes from the subscription that is currently selected. If a header disappears from a later update, the restriction is lifted.
- These are interface restrictions, not protection. A profile from a file or from another link without the headers is accepted without them. Values already entered stay and keep working.
- The app shows Changes are disabled by the provider on a restricted page.
Found a mistake? Open an issue on GitHub.