Feature #7458
closed
Automatically update changed JavaScripts
Added by Evgeny Novikov over 7 years ago.
Updated over 4 years ago.
Description
Now if Bridge comes with some new JavaScripts they aren't automatically updated and browser caches keep the old ones until they will be cleaned up somehow. I am not sure whether the development Django web server or/and Apache are responsible for this.
- Status changed from New to Feedback
- Status changed from Feedback to Open
I still suppose that the really production server, which Bridge is, has to update caches like this is done by other well known servers. Actually everybody are bothered with this issue very much. For instance, I completely switched of caches, Ilja restarts the whole web-browser when he meets unexpected things in Bridge. This does take much time after all. The only place where this issue doesn't hit is automatically deployed instances or containers, but they aren't intended to be updated at all in the most cases.
- Priority changed from High to Urgent
- Target version set to 3.0
It turned out that there is a nice solution for this issue. Let's implement it, since scripts are updated often that can cause unpleasant consequences.
- Status changed from Open to Resolved
Implemented in branch klever-3.0.
- Status changed from Resolved to Closed
In master. Everybody can switch on browser caches!
Also available in: Atom
PDF