Provider headers

The complete integration reference is currently in Russian. Key headers include Profile-Title, Profile-Web-Page-URL, Profile-Web-Page-Title, Support-URL, Profile-Update-Interval, Profile-Buttons, Profile-Theme/Qmesh-Theme and Routing.

Themes accept a single JSON object or an array, encoded once as base64: plus Base64 UTF-8 when needed. Download the theme array example. Users preview and explicitly confirm the chosen theme.

The Routing header accepts qmesh://routing/onadd/<Base64 JSON> (add and enable), qmesh://routing/add/<Base64 JSON> (add without enabling) or qmesh://routing/off (disable while retaining the profile). Encode the profile JSON object as Base64 UTF-8. Database sources inside the profile use Geositeurl and Geoipurl.

Profile-Geosite-URL / Profile-Geoip-URL (or Qmesh- aliases) set direct HTTPS database sources with priority over routing-profile and local URLs. Header sources are fetched and attached automatically during connection preparation.

Subscription requests may include a hashed X-Hwid. Treat it as an opaque identifier and allow binding resets. Compatibility retries may use Happ/Qmesh <version> as User-Agent. Do not depend on one exact app version.