Hi again,
yes I see that FF does show wrong ASCII chars so that the problem.Also there is no hex view in FF or Chrome where you could see the right hex bytes you could copy and convert to ASCII.Anyway.
So I checked the site again to see how you get access to the keyfile site and there are only 2 sites called.The first site to prepair the access / allowing to the keyfile site.The first site you can call always successfully and from there you only need to grab the PHPSESSID=* value and the SERVERID=* which you now can use with the keyfile site to make a new request.So this you have to do very quick (just have 3 seconds time) to get successfully access and response = keyfile bytes instead to get status 403 forbidden.
Thats all.
Code:
http://drmapi.protv.ro/hlsengine/prepare/
http://drmapi.protv.ro/keys/get/protvplus.ro/61307737
So I am not very common with ffmpeg tool but somehow it should be maybe possible to tell ffmpeg or set paramaters what to do and how to access and prepair the keylink from the playlist.Something like this....
Code:
ffmpeg -i "playlist_link.m3u8" -prelink "http://drmapi.protv.ro/hlsengine/prepare/" (PHPSESSID=*),(SERVERID=*)
...just a idea you know so I dont know whether ffmpeg has such features or not to build something like this.But if so then ffmpeg could read the prepair link first to grab the set cookie paramters from response and to use it if it does access the keyfile link from playlist to get a successfully access to this link to prevent a forbidden access.
greetz