Single stream playlist.m3u8 files use relative paths:
#EXTM3U
#EXT-X-VERSION:2
#EXT-X-STREAM-INF:PROGRAM-ID=1,BANDWIDTH=590691,CODECS="avc1.77.30, mp4a.40.2",RESOLUTION=640x360
playlist.m3u8?wowzasessionid=1077203360
Name group (ngrp) playlist.m3u8 files use “domain-absolute” paths:
#EXTM3U
#EXT-X-VERSION:2
#EXT-X-STREAM-INF:PROGRAM-ID=1,BANDWIDTH=891331,CODECS="avc1.77.31,mp4a.40.2",RESOLUTION=896x504
/livetc/_definst_/mp4:livetc.mp4_source/playlist.m3u8?wowzasessionid=1267048161
#EXT-X-STREAM-INF:PROGRAM-ID=1,BANDWIDTH=548036,CODECS="avc1.77.30,mp4a.40.2",RESOLUTION=640x360
/livetc/_definst_/mp4:livetc.mp4_360p/playlist.m3u8?wowzasessionid=1267048161
Is it possible to force name group playlist.m3u8 files to use FQDN or “full absolute” paths? Example:
#EXTM3U
#EXT-X-VERSION:2
#EXT-X-STREAM-INF:PROGRAM-ID=1,BANDWIDTH=891331,CODECS="avc1.77.31,mp4a.40.2",RESOLUTION=896x504
http://[server]/livetc/_definst_/mp4:livetc.mp4_source/playlist.m3u8?wowzasessionid=1267048161
#EXT-X-STREAM-INF:PROGRAM-ID=1,BANDWIDTH=548036,CODECS="avc1.77.30,mp4a.40.2",RESOLUTION=640x360
http://[server]/livetc/_definst_/mp4:livetc.mp4_360p/playlist.m3u8?wowzasessionid=1267048161
This would enable us to use JW player until they update their adaptive provider to support domain-absolute paths.