Custom menu links & caching

[LeviSnoot]

This is really valuable info Rezer, I'm now led to believe the root cause of this issue is a Jellyfins service workers. I found a Github issue that appears to corroborate this: https://github.com/jellyfin/jellyfin-web/issues/4549

So what happens is, this service worker puts the entire /web/ directory in the visitors browser cache, and this directory includes among other files related to serving the web client to users, config.json.

There's a PR that is trying to mitigate this: https://github.com/jellyfin/jellyfin-web/pull/4885

Looks like we're not alone in finding this behaviour odd, and hopefully the PR gets merged so future versions of JF won't have this issue. For the time being though, I'm not sure how to work around it, but if I think of something, I'll update the thread!