Flussonic compatibility¶
Sapsan answers on the familiar Flussonic Media Server URLs so existing players, integrations, and monitoring keep working during migration. Compatibility is on by default and can be disabled in the config:
flussonic:
streaming: false # default true
Supported legacy URLs¶
Root-level addresses of the following forms are recognized (GET/HEAD/OPTIONS only):
| Legacy URL | What it does |
|---|---|
/<stream>/variant/v1/index.m3u8 |
track playlist |
/<stream>/info.json |
stream information |
/<stream>/ranges.json |
recorded archive ranges |
/<stream>/<utc>-preview.mp4 |
MP4 preview of an archive moment |
/<stream>/index-<from>-<duration>.fmp4.m3u8 |
archive HLS playlist; redirects (302) to /streaming/v/<stream>/index.m3u8?from=&to=, converting seconds to milliseconds |
ranges.json parameters: closed_at_gte, opened_at_gte, opened_at_lte, resolution, limit, cursor.
Admin API v3¶
The API under the /streamer/api/v3 prefix responds in the Flussonic Streamer API v3 format — see Admin API. When converting a v3 configuration, some fields are dropped by design (static, comment, title, segment_duration, https listeners, and others) — a loss report is available during conversion.
Tokens¶
As in Flussonic, a token is accepted both as ?token= in the URL and as an Authorization: Bearer header (the header takes priority).