[BUG] HLS input with relative path

[Damien_Leroy]

Using the Wowza Streaming Engine to ingest HLS (following instructions of https://www.wowza.com/docs/how-to-publish-and-play-a-live-stream-apple-hls), I noticed that the ingest is not working correctly when the chunks are relative.

In practice, in a playlist located at http://domain.com/a_path/playlist.m3u8 which contains the following lines:

...
#EXTINF:4.00,
/another_path/chunk1.ts
...

… the chunk is supposed to be located at http://domain.com/another_path/chunk1.ts. It is how it is interpreted in all players that I know.

Wowza does looks for this file at http://domain.com/a_path/another_path/chunk1.ts, which would correspond to the following content:

#EXTINF:4.00,
another_path/chunk1.ts

This problem makes the HLS ingestion fail when the chunk paths are relative and the playlist is not at the root of the domain.

[Shaun_Procter]

Not sure if I have read the issue correctly. For deeper paths I find you need to use definst in the path like this when referencing the playlist m3u8 file that Wowza generates,

http:///<application_name>/definst/<dir_1_name>/<dir_2_name>/<stream_name/playlist.m3u8

e.g. where,

address = somecompany.com

application_name = live

dir_1_name = 1

dir_2_name = 2

stream_name = 1.sdp

http://somecompany.com/live/definst/1/2/1.sdp/playlist.m3u8

[Hector_Claudio]

I have the exact same problem. No resolution yet. Anyone has an answer please help, because this is rediculuous that I’m using two big hitters in the Industry (Akamai and Wowza) and something as simple as this has been an issue for over 6 to 8 months. Just parsing a url is TRIVIAL.