Extra overriding #EXT-X-KEY wishlist

[mvallevand]

I am trying to write an extra that involves sending back an m3u8 containing an AES key

#EXT-X-KEY:METHOD=AES-128,URI="...",IV=0x30303030303030303030303067020c0b,KEYFORMAT="identity"

but unfortunately the URI requires two cookies and some headers.

I haven't been able to make NextPVR accept passed cookies and I am not sure if NextPVR uses passed headers either when it fetches the key either, I couldn't see any logging on getting the key.   

My first wishlist is that cookies could accepted from Extras (I and guess m3u8 files), perhaps using the Kodi method opf muitiple Set-Cookie= pipes on the url.  These are huge though and in my use case only needed for the key.

My second wishlist which might be easier is providing an option allowing a override the URI.  The extra could write the key to file and NextPVR could use that files instead of the URI to get the key.

Martin

[sub]

Today is not a good day for me to look at this. Busy with day job stuff. Remind me another day and I'll help you work through it.

It looks like it should pass through headers from the m3u8 url to any requests, including key urls. I suspect it wouldn't do cookies currently.

[mvallevand]

No worries very low priority, probably I should get used to building Docker servers instead. If you already pass through headers to the key URI I guess the Set-Cookie approach could be more flexible for others.

Martin

[mvallevand]

It started streaming again today so I am wondering if the source site was not setting the cookie properly, this was a new change for them.

I also confirmed with my proxy that a passed user agent is working and I see the two keys in the cookie too, so the cookies must simply be in the NextPVR session started with the m3u8 file.

Martin

[sub]

Great