[ZBX-15905] Versioning of browser cached files Created: 2018 Aug 29 Updated: 2020 Sep 16 Resolved: 2020 Sep 15 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Frontend (F) |
Affects Version/s: | None |
Fix Version/s: | None |
Type: | Problem report | Priority: | Trivial |
Reporter: | Ingus Vilnis | Assignee: | Zabbix Development Team |
Resolution: | Won't fix | Votes: | 4 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Issue Links: |
|
||||||||||||||||||||||||
Team: | Team D | ||||||||||||||||||||||||
Sprint: | Sprint 50 (Mar 2019), Sprint 51 (Apr 2019), Sprint 52 (May 2019) |
Description |
Every time after frontend upgrade you have to do Ctrl + Shift + R to force reload of static content cached by the browser. Experience users remember to do this when the suspect broken layout after upgrade but you can't expect this from all users and TV screens in a large organisation. How about introducing versioning of affected CSS, javascript, image etc file names (e.g. styles/dark-theme_v401.css) which change upon every upgrade thus forcing the browsers to reload them automatically? |
Comments |
Comment by Gregory Chalenko [ 2019 Apr 05 ] |
POC solution based on file caching mechanism is implemented in svn://svn.zabbix.com/branches/dev/ZBX-15905. |
Comment by Gregory Chalenko [ 2019 Apr 11 ] |
RESOLVED in development branch svn://svn.zabbix.com/branches/dev/ZBX-15905. |
Comment by Gregory Chalenko [ 2019 May 03 ] |
Implemented in:
|
Comment by Gregory Chalenko [ 2019 May 29 ] |
Documentation changes: |
Comment by dimir [ 2019 Jun 04 ] |
Please also revert the font replacement changes. yurii, please also remember that new packages should work in 3 ways:
Same for 4.2.3 . <yurii> It was decided to keep fonts in the assets directory. Will provide a packaging fix. |
Comment by Stefan Radman [ 2019 Jun 05 ] |
The changes have broken 4.0.8 on CentOS. If you look through the forums you'll see that people are implementing all kinds of insecure workarounds (chmod 777, disable SELinux) because of the assets cache to make 4.0.8 work on CentOS and Ubuntu. IMHO this new feature (versioning) should never have been included in a minor bugfix release. |
Comment by Vjaceslavs Bogdanovs [ 2019 Jun 05 ] |
stefan.radman, this is a known issue and our team is doing our best to fix this problem. |
Comment by dimir [ 2019 Jun 06 ] |
This issue introduced regression: so the implementation was rolled back, see this comment for details. Re-implemented in |