HTTP headers overview
Which requests Letakof makes and where they go.
To load a subscription, Letakof sends an ordinary HTTP request to the address you entered and reads the headers of the response.
- Additional headers:
letakof-*headers a provider can add. - Available headers: what Letakof sends and reads.
- Device identifier (HWID): how it is made and how to turn it off.
Requests Letakof makes
| Request | Goes to | When | What is sent |
|---|---|---|---|
| Subscription | The address you entered | Adding, refreshing, automatic update | User-Agent, Accept and, if Send HWID is on, four device headers |
| Rule sets | Addresses from your profile | With the subscription update, then on a schedule | User-Agent only |
| GEO databases | The default or your own address | On the button; weekly if auto-update is on (off by default) | User-Agent only |
| Provider logo, group icons | Addresses from your profile (https) | Once per address | An image request, no device headers |
| Latency test | GStatic, Google or Cloudflare, as you chose | When you measure, and for automatic groups | Made by the core through the tested server |
| Updates | GitHub (update feed and release file) | About once a day if enabled, and on demand | A standard request from the updater. iPhone has none: the App Store updates it |
| Modules (iPhone) | HTTPS addresses you or the module give | When you add or update a module | User-Agent: Letakof-Modules/1, no device headers |
| TV activation | A TV on your local network | When you press Send | The subscription link, over plain HTTP inside the network |
Device headers go only to the subscription address, that is to your provider. Letakof has no analytics or crash reports and sends nothing to Lekavot Limited.
Found a mistake? Open an issue on GitHub.