Web front-end release issues

1, the reason is that the company has made a background management system ( technical framework is Vue, UI library is using Element ui ) this system has been used by many users.
2. The original release method was to package it locally and put it on the server, but on that day I wanted to use the automatic release method (a set of publishing system developed by the company, the js version number will change every time). There was a problem the second day after the release, and many users could not load the latest resources, resulting in the left click not moving (because my left menu route adopts lazy loading mode. The latest resources can not be loaded by the browser reported an error), I can only let them refresh, but some users have serious browser cache, so they have to force ctrl + f5 to refresh .
3. I would like to ask some other big companies that the front-end release method is how to avoid the user who happens to be in use when the system is being released. In this case, he must be allowed to take the initiative to refresh the of this problem. Thank you. (the solution you can think of now can save the most recently released versions with CDN, and then regularly remove the oldest resources.)

Php html javascript node.js java
Jun.11,2021

the root cause of this problem should be that the html page of the system is cached and the resource requested in the html page is still the resource before release, causing the problem.
can prevent browsers from caching html page information. 

<meta HTTP-EQUIV="pragma" CONTENT="no-cache"> 
<meta HTTP-EQUIV="Cache-Control" CONTENT="no-store, must-revalidate"> 
<meta HTTP-EQUIV="expires" CONTENT="0">
  1. it's OK not to delete old resources, but there is little consumption of JS and CSS,
  2. use HTTP header to control the cache of all resources, you can look for solutions, a lot of introduction articles. The point is that you need to find a way to use the same strategy, so that some of them are out of date and some are still caching.
  3. in general, if your new version is helpful to users, they will be willing to cooperate with your refresh strategy. More often, each version of the interface has to be retained in the background, which is less likely to be incompatible. You can read the version information regularly and prompt the user to refresh.

Previous: Why can't pandas dataframe output column values be aligned separately?

Next: Spirng transaction (optimistic lock) problem?

css mysql arrays josn react html typescript webpack npm sass R objective-c .net sql-server jquery python-3.x angularjs django angular excel regex iphone ajax linux xml pandas vba spring database wordpress string wpf xcode windows bash postgresql oracle multithreading eclipse list firebase algorithm macos forms image scala visual-studio azure bootstrap spring-boot react-native python-2.7 docker performance function winforms matlab powershell apache dataframe api sqlite numpy rest shell selenium flutter dart maven loops qt swing android-studio csv express file class tensorflow sorting codeigniter perl
© 2021 CodesHelper
Advertising Contact us About us
Menu