缓存破坏:附加查询字符串或重命名文件? [英] Cache busting: append query string or rename file?

查看:33
本文介绍了缓存破坏:附加查询字符串或重命名文件?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

当我们尝试破坏静态资源缓存时,有两种常用方法:

When we try to break static assets caches, there are two common ways to doing that:

  1. 通过附加查询字符串,如 assets/file.ext?v=123abc

通过重命名文件,如 assets/file.123abc.ext

但是经过几天的搜索,我发现大多数构建工具都喜欢重命名文件,例如gulp-rev.在我看来,这种修订会在服务器上生成大量文件块:

However after days of searching, I found that most of building tools prefer to renaming files, e.g. gulp-rev. In my view this kind of revision will generates lots of file chunks on the server:

assets
 |_ file.a.ext
 |_ file.b.ext
 |_ file.c.ext
 |_ file.d.ext
 |...

对此有什么想法吗?

推荐答案

经过几天的搜索,我发现了一些有趣的查询字符串解决方案(assets/file.ext?v=123abc):

After days of searching, I found something interesting for query string solution (assets/file.ext?v=123abc):

如果我们使用 CDN 服务静态资产,动态页面和静态资产是分开托管的.一旦我们要发布一个新版本的应用,就会发生冲突:应该先更新哪部分资源?

If we use CDN to serve static assets, dynamic pages and static assets are hosted separately. Once we want to publish a new version of app, the conflict occurs: which part of the resources should be updated first?

  1. 页面优先.如果用户在您更新动态页面后立即访问您的网站,则资产将指向新版本,例如assets/file.ext?v=456def,然后浏览器下载旧资产并将其缓存为新版本,不幸的是这些用户永远无法获得正确的资源.

  1. Pages first. If users visit your site right after you updated dynamic pages, the assets are pointing to new versions, e.g. assets/file.ext?v=456def, then browsers download old assets and cache them as new version, unluckily those users will never get the right resources.

资产优先.假设有一些新用户在新版本资产发布后立即访问您的网站,旧页面和新脚本,啊哈!可能会出现一些致命错误,您的网站会变得很糟糕!

Assets first. Assuming there're some new users go to your site right after new version of assets are published, the old page and the new scripts, aha! There may be some deadly errors and your site gets boooooom!

所以重命名文件(assets/file.123abc.ext)的解决方案来了.不同版本的文件命名不同,因此它们不会相互覆盖.因此,我们先更新资产,然后更新页面,一切都按预期进行,哇哦!

So here comes the solution of renaming files (assets/file.123abc.ext). Different versions of files are named differently, so they will not overwrite each other. Therefore we updated assets first, then the pages, everything goes as expected, woohoo!

更多详情请阅读这篇文章(中文):https://www.zhihu.com/question/20790576/answer/32602154

For more details please read this article(Chinese): https://www.zhihu.com/question/20790576/answer/32602154

这篇关于缓存破坏:附加查询字符串或重命名文件?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆