OTT Navigator

The app's default User-Agent

Unless something else is set, the app identifies itself in the User-Agent header like this:

For example OTT Navigator/1.7.5.2 (Linux;Android 12; en; HASH) and OTT Navigator/1.7.5.2 (Linux;Android 12; HASH) ExoPlayerLib/2.x.x (there is no space after Linux;).

What changes it

The first one found of these is used for stream requests:

  1. The app-wide setting Settings > Extended settings > System settings > Network > HTTP User-Agent (not shown in Simplified mode). It also replaces the default for all other requests of the app. Besides a value of one’s own it offers browser presets: Chrome (Windows), Firefox (Windows), Safari (macOS), Chrome (Android), VLC (since 1.7.5.2).
  2. A User-Agent among the channel’s HTTP headers: #EXTHTTP or stream_headers in an M3U playlist, headers in OTC, or the headers in the provider’s properties.
  3. The channel’s own User-Agent: #EXTVLCOPT:http-user-agent, |User-Agent= after the stream URL, user_agent in OTC.
  4. The provider’s HTTP User Agent (Content) in its properties, then HTTP User Agent (API).
  5. The default above.

The playlist itself is downloaded with the provider’s HTTP User Agent (API) when it is set, otherwise with the app-wide setting or the default. Providers connected through their API (portals and others) may send a User-Agent of their own.