While doing HLS AES 128 playback, the player request key file for every chunk. about http-streaming HOT 11 CLOSED

I found @benvirus had fixed this problem by check key uri and store the key: https://github.com/videojs/videojs-contrib-hls/pull/865/files/87304c6c544d8eecd7de90acdd1685e7ee75a998..d308332bb58c6734aa6a3bc15a9a4a836997faa8
but in newer version it's not working anymore.My hls segments encypt with one key file,so the key uri is the same at all.can you add a option like "StoreKey:true",that will be good news for someone like me.

from http-streaming.

Just add this to your options and it will be cached. I was suffering from the same issue with latest build, and finally figured it out

html5: {
    vhs: {
      cacheEncryptionKeys: true
    }
  }

notice the vhs, not hls :)

from http-streaming.

Hey @riubin , why is it that the cache expires can't be set by the server?

from http-streaming.

Because the php server need check the session info by valid user that can watch the video. whatever, whether or not set cache expires the php server will be very hevy,but I do not want waste the resource of server. I think any others should have the problems too.
Thank you~

from http-streaming.

Add: The key file will be send to client by php script.client can't get key file directly.

from http-streaming.

Hey @riubin , the problem with caching the key requests by the player is if the keys do expire, the player has no way of knowing to fetch it again from the server. That's why the cache expires header is useful, and the caching can be done outside of the player.

from http-streaming.

You can fork the repo, add the cache key feature like me.

from http-streaming.

We'll review videojs/videojs-contrib-hls#1433 and add this feature to the project

from http-streaming.

👋 Thanks for opening your first issue here! 👋

If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can.
To help make it easier for us to investigate your issue, please follow the contributing guidelines.

from http-streaming.

Seems related to #140

from http-streaming.

While we believe appropriate cache-control headers are the optimal solution, we've added an option to not re-request the key on every segment (#446). It is out in version 1.10.0.

from http-streaming.