Board Game Arena

I'm not sure who to file a bug against. I don't think there is a bug per se in the studio server, since it appears to deliver the correct file when asked, and supplies things like the ETag and other headers that clients and caching intermediaries can use to do cache staleness checking. The behavior manifested on several different browsers, including Vivaldi (a Chrome-based browser) on Linux, Safari on MacOS, and Chrome on Windows. It only went away after the browser caches were manually cleared. I imagine I could try to document a series of steps to reproduce it, but there are a lot of variables at play here, and it doesn't seem a good use of my time right now.

This was the reason I asked in the OP if a shortened cache period might be appropriate here -- it doesn't fix the problem directly, but mitigates it to some degree. I completely understand if the admins here don't want to change the delivered cache lifetime on files the server delivers. It's their system, their rules and policies.