You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running into issues where static assets are cached by the user (intended, of course), but where we'd ideally like to have assets expired the moment NodeBB is updated.
So if caching is on (NODE_ENV is not development), add a cache buster equal to the timestamp retrieved via the git log.
I've been having problems with this issue as well at times and would often need to clear my cache. I figured it was just me but I guess not, so I'm glad this will be implemented. 👍
Running into issues where static assets are cached by the user (intended, of course), but where we'd ideally like to have assets expired the moment NodeBB is updated.
So if caching is on (
NODE_ENV
is notdevelopment
), add a cache buster equal to the timestamp retrieved via the git log.The text was updated successfully, but these errors were encountered: