Server Version#: 1.21.3
Player Version#:
So this isn’t really a bug problem and I’ve seen this sporadically pop up but I would like to know the reasoning behind it. Each user has it’s own cache key, or perhaps even each playback regenerates the cache key so it’s pretty much impossible to use a reverse proxy to cache the content even though it’s fetching from the same source file.
Is this is due to how the database works or is there some other reason?
Each session is unique and is the way the server/client communication is designed (It is how we can track watched progress and status, along with ensuring that the server is producing the right transcoder output (if required) for that session.
A combination of tokens and the path uuid I take it?
I don’t know the exact method the unique session key is made. but I don’t think is it just two keys combined. Unfortunately it is late and the folks I could ask are not around at the moment.
Gotcha, I’m curious as how to you guys do it
Just bumping this post
Curious what you need the info for. Why does it matter.
I know this is close sourced code but it would useful for me for my own learning I suppose. I just wanna test how scalable this is if let’s say I make my own cluster for my own personal viewing when I travel, using reverse proxies to cache would be cool. Jellyfin allows for this, and it tracks the session too. Usualy that’s done on cookies, so I wonder what makes Plex do something different
