blocks|key|1379346|text|如果这是关于.css和.js的更改，一种方法是“缓存崩溃”，即在每个版本的文件名后附加类似"_versionNo“的内容。例如：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1379347|script_1.0.css+//+This+is+the+URL+for+release+1.0
script_1.1.css+//+This+is+the+URL+for+release+1.1
script_1.2.css+//+etc.|code-block|syntax|javascript|1379348|或者，在文件名之后执行此操作：|1379349|script.css?v=1.0+//+This+is+the+URL+for+release+1.0
script.css?v=1.1+//+This+is+the+URL+for+release+1.1
script.css?v=1.2+//+etc.|1379350|你可以查看这个link，看看它是如何工作的。|1379351|entityMap|0|LINK|mutability|MUTABLE|url|http://www.htmlgoodies.com/tutorials/getting_started/article.php/3479551^0|6|4|B|3|1A|A|0|0|0|0|7|4|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@$9|Z|A|10|B|C]|$9|11|A|12|B|C]|$9|13|A|14|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|15|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|16|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|17|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|18|8|@]|D|@$9|19|A|1A|1|1B]]|E|$]]|$1|Q|3|-4|5|6|7|1C|8|@]|D|@]|E|$]]]|R|$S|$5|T|U|V|E|$W|X]]]]

If this is about <code>.css</code> and <code>.js</code> changes, one way is to to "cache busting" is by appending something like "<code>_versionNo</code>" to the file name for each release. For example:



<pre class="lang-none prettyprint-override"><code>script_1.0.css // This is the URL for release 1.0
script_1.1.css // This is the URL for release 1.1
script_1.2.css // etc.
</code></pre>

Or alternatively do it after the file name:

<pre class="lang-none prettyprint-override"><code>script.css?v=1.0 // This is the URL for release 1.0
script.css?v=1.1 // This is the URL for release 1.1
script.css?v=1.2 // etc.
</code></pre>

You can check out this <a href="http://www.htmlgoodies.com/tutorials/getting_started/article.php/3479551" rel="noreferrer">link</a> to see how it could work.

blocks|key|1379321|text|查看cache-control和expires元标记。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1379322|<META+HTTP-EQUIV="CACHE-CONTROL"+CONTENT="NO-CACHE">|style|CODE|1379323|<META+HTTP-EQUIV="EXPIRES"+CONTENT="Mon,+22+Jul+2002+11:12:01+GMT">|1379324|另一种常见的做法是将不断变化的字符串附加到所请求文件的末尾。例如：|1379325|<script+type="text/javascript"+src="main.js?v=12392823"></script>|1379326|entityMap|0|LINK|mutability|MUTABLE|url|http://www.i18nguy.com/markup/metatags.html|1^0|2|D|0|G|7|1|0|0|1G|0|0|1V|0|0|0|1T|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@$A|X|B|Y|1|Z]|$A|10|B|11|1|12]]|C|$]]|$1|D|3|E|5|6|7|13|8|@$A|14|B|15|F|G]]|9|@]|C|$]]|$1|H|3|I|5|6|7|16|8|@$A|17|B|18|F|G]]|9|@]|C|$]]|$1|J|3|K|5|6|7|19|8|@]|9|@]|C|$]]|$1|L|3|M|5|6|7|1A|8|@$A|1B|B|1C|F|G]]|9|@]|C|$]]|$1|N|3|-4|5|6|7|1D|8|@]|9|@]|C|$]]]|O|$P|$5|Q|R|S|C|$T|U]]|V|$5|Q|R|S|C|$T|U]]]]

Look into the <a href="http://www.i18nguy.com/markup/metatags.html" rel="noreferrer">cache-control</a> and the <a href="http://www.i18nguy.com/markup/metatags.html" rel="noreferrer">expires</a> META Tag.

<code>&lt;META HTTP-EQUIV="CACHE-CONTROL" CONTENT="NO-CACHE"&gt;</code> 
<code>&lt;META HTTP-EQUIV="EXPIRES" CONTENT="Mon, 22 Jul 2002 11:12:01 GMT"&gt;</code>

Another common practices is to append constantly-changing strings to the end of the requested files. For instance:

<code>&lt;script type="text/javascript" src="main.js?v=12392823"&gt;&lt;/script&gt;</code>

blocks|key|1164385|text|不是这样的。一种方法是在传递内容时发送适当的头部，以强制浏览器重新加载：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1164386|Making+sure+a+web+page+is+not+cached,+across+all+browsers.|offset|length|1164387|如果你在SO上搜索"cache+header"或类似的东西，你会找到ASP.NET特有的例子。|style|CODE|1164388|另一种不太干净但有时只能在服务器端控制头部的方法是向被调用的资源添加一个随机的GET参数：|1164389|myimage.gif?random=1923849839|code-block|syntax|javascript|1164390|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/49547/making-sure-a-web-page-is-not-cached-across-all-browsers^0|0|0|1M|0|0|9|E|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@]|9|@$D|10|E|11|1|12]]|A|$]]|$1|F|3|G|5|6|7|13|8|@$D|14|E|15|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|16|8|@]|9|@]|A|$]]|$1|L|3|M|5|N|7|17|8|@]|9|@]|A|$O|P]]|$1|Q|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|X]]]]

Not as such. One method is to send the appropriate headers when delivering content to force the browser to reload:

<a href="https://stackoverflow.com/questions/49547/making-sure-a-web-page-is-not-cached-across-all-browsers">Making sure a web page is not cached, across all browsers.</a>

If your search for <code>"cache header"</code> or something similar here on SO, you'll find ASP.NET specific examples.

Another, less clean but sometimes only way if you can't control the headers on server side, is adding a random GET parameter to the resource that is being called:

<pre><code>myimage.gif?random=1923849839
</code></pre>

blocks|key|1164783|text|我有一个案例，我会在网上拍摄客户的照片，如果照片发生变化，我需要更新div。浏览器仍在显示旧照片。因此，我使用了调用随机GET变量的技巧，该变量每次都是唯一的。这就是如果它能帮助任何人的话|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1164784|<img+src="/photos/userid_73.jpg?random=<?php+echo+rand()+?>"+...|code-block|syntax|javascript|1164785|正如其他人指出的那样，以下是更有效的解决方案，因为它只会在图像发生更改时重新加载图像，并通过文件大小识别这种更改：|1164786|<img+src="/photos/userid_73.jpg?modified=<?+filemtime("/photos/userid_73.jpg")?>"|1164787|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

I had a case where I would take photos of clients online and would need to update the div if a photo is changed. Browser was still showing the old photo. So I used the hack of calling a random GET variable, which would be unique every time. Here it is if it could help anybody

<pre><code>&lt;img src="/photos/userid_73.jpg?random=&lt;?php echo rand() ?&gt;" ...
</code></pre>

EDIT
As pointed out by others, following is much more efficient solution since it will reload images only when they are changed, identifying this change by the file size:

<pre><code>&lt;img src="/photos/userid_73.jpg?modified=&lt;? filemtime("/photos/userid_73.jpg")?&gt;"
</code></pre>

blocks|key|1164904|text|许多答案都没有抓住要点--大多数开发人员都很清楚关闭缓存是低效的。然而，在许多常见情况下，效率并不重要，并且默认缓存行为被严重破坏。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1164905|其中包括嵌套的、迭代的脚本测试(最重要的！)和损坏的第三方软件解决方案。这里给出的解决方案都不足以解决这种常见的情况。大多数web浏览器的缓存过于激进，没有提供合理的方法来避免这些问题。|1164906|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

A lot of answers are missing the point - most developers are well aware that turning off the cache is inefficient. However, there are many common circumstances where efficiency is unimportant and default cache behavior is badly broken.

These include nested, iterative script testing (the big one!) and broken third party software workarounds. None of the solutions given here are adequate to address such common scenarios. Most web browsers are far too aggressive caching and provide no sensible means to avoid these problems.

blocks|key|1165032|text|将URL更新为以下内容对我来说是可行的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1165033|/custom.js?id=1|offset|length|style|CODE|1165034|通过在?id=之后添加一个唯一的数字并为新的更改递增该数字，用户不必按CTRL+%2B+F5来刷新缓存。或者，可以在?id=之后附加当前时间或纪元的散列或字符串版本|1165035|像?id=1520606295这样的东西|1165036|entityMap^0|0|0|F|0|3|4|Z|9|1K|4|0|1|E|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@$D|P|E|Q|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@$D|S|E|T|F|G]|$D|U|E|V|F|G]|$D|W|E|X|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|Y|8|@$D|Z|E|10|F|G]]|9|@]|A|$]]|$1|L|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|M|$]]

Updating the URL to the following works for me:

<code>/custom.js?id=1</code>

By adding a unique number after <code>?id=</code> and incrementing it for new changes, users do not have to press <code>CTRL + F5</code> to refresh the cache. Alternatively, you can append hash or string version of the current time or Epoch after <code>?id=</code>

Something like <code>?id=1520606295</code>

blocks|key|1164613|text|<meta+http-equiv="pragma"+content="no-cache"+/>|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|1164614|另请参阅https://stackoverflow.com/questions/126772/how-to-force-a-web-browser-not-to-cache-images|unstyled|offset|length|1164615|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/126772/how-to-force-a-web-browser-not-to-cache-images^0|0|4|2H|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|R|8|@]|9|@$G|S|H|T|1|U]]|A|$]]|$1|I|3|-4|5|F|7|V|8|@]|9|@]|A|$]]]|J|$K|$5|L|M|N|A|$O|P]]]]

<pre><code>&lt;meta http-equiv="pragma" content="no-cache" /&gt;
</code></pre>

Also see <a href="https://stackoverflow.com/questions/126772/how-to-force-a-web-browser-not-to-cache-images" title="this">https://stackoverflow.com/questions/126772/how-to-force-a-web-browser-not-to-cache-images</a>

blocks|key|1164521|text|Here是在ASP.NET中设置缓存的MDSN页面。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1164522|Response.Cache.SetExpires(DateTime.Now.AddSeconds(60))
Response.Cache.SetCacheability(HttpCacheability.Public)
Response.Cache.SetValidUntilExpires(False)
Response.Cache.VaryByParams("Category")+=+True

If+Response.Cache.VaryByParams("Category")+Then
+++'...
End+If|code-block|syntax|javascript|1164523|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/system.web.httpresponse.cache%2528VS.71%2529.aspx^0|0|4|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@$A|R|B|S|1|T]]|C|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|C|$G|H]]|$1|I|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]]]

<a href="http://msdn.microsoft.com/en-us/library/system.web.httpresponse.cache%28VS.71%29.aspx" rel="nofollow noreferrer">Here</a> is the MDSN page on setting caching in ASP.NET.

<pre><code>Response.Cache.SetExpires(DateTime.Now.AddSeconds(60))
Response.Cache.SetCacheability(HttpCacheability.Public)
Response.Cache.SetValidUntilExpires(False)
Response.Cache.VaryByParams("Category") = True

If Response.Cache.VaryByParams("Category") Then
 '...
End If
</code></pre>

blocks|key|1164695|text|我不确定这是否真的对你有帮助，但这就是缓存在任何浏览器上的工作方式。当浏览器请求一个文件时，它应该总是向服务器发送一个请求，除非有“离线”模式。服务器将读取一些参数，如date+modified或etags。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1164696|服务器将返回未修改的304错误响应，浏览器将必须使用其缓存。如果etag没有在服务器端验证，或者修改日期低于当前修改日期，服务器应该返回带有新修改日期和/或etag的新内容。|1164697|如果没有缓存数据发送到浏览器，我猜行为是不确定的，浏览器可能缓存也可能不缓存不知道它们是如何缓存的文件。如果您在响应中设置缓存参数，它将正确缓存您的文件，然后服务器可能会选择返回304错误或新内容。|1164698|这就是应该怎么做的。在urls中使用随机参数或版本号更像是一种黑客行为。|1164699|http://www.checkupdown.com/status/E304.html+http://en.wikipedia.org/wiki/HTTP_ETag+http://www.xpertdeveloper.com/2011/03/last-modified-header-vs-expire-header-vs-etag/|offset|length|1164700|看完后，我看到还有一个过期日期。如果您有问题，可能是您设置了过期日期。换句话说，当浏览器缓存你的文件时，因为它有一个过期日期，所以它不应该在该日期之前再次请求它。换句话说，它永远不会向服务器请求文件，也永远不会收到304+not+modified。它将简单地使用缓存，直到到达过期日期或清除缓存。|1164701|所以这就是我的猜测，你有某种到期日期，你应该使用最后修改的etags或它们的组合，并确保没有到期日期。|1164702|如果人们倾向于刷新很多，并且文件不会有太多更改，那么设置一个较大的到期日期可能是明智的。|1164703|我的两分钱！|1164704|entityMap|0|LINK|mutability|MUTABLE|url|http://www.checkupdown.com/status/E304.html|1|http://en.wikipedia.org/wiki/HTTP/_ETag|2|http://www.xpertdeveloper.com/2011/03/last-modified-header-vs-expire-header-vs-etag/^0|0|0|0|0|0|17|0|18|12|1|2B|2C|2|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|15|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|16|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|17|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|18|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|19|8|@]|9|@$J|1A|K|1B|1|1C]|$J|1D|K|1E|1|1F]|$J|1G|K|1H|1|1I]]|A|$]]|$1|L|3|M|5|6|7|1J|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|1K|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1L|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|1M|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|1N|8|@]|9|@]|A|$]]]|U|$V|$5|W|X|Y|A|$Z|10]]|11|$5|W|X|Y|A|$Z|12]]|13|$5|W|X|Y|A|$Z|14]]]]

Not sure if that might really help you but that's how caching should work on any browser. When the browser request a file, it should always send a request to the server unless there is a "offline" mode. The server will read some parameters like date modified or etags. 

The server will return a 304 error response for NOT MODIFIED and the browser will have to use its cache. If the etag doesn't validate on server side or the modified date is below the current modified date, the server should return the new content with the new modified date or etags or both. 

If there is no caching data sent to the browser, I guess the behavior is undetermined, the browser may or may not cache file that don't tell how they are cached. If you set caching parameters in the response it will cache your files correctly and the server then may choose to return a 304 error, or the new content. 

This is how it should be done. Using random params or version number in urls is more like a hack than anything. 

<a href="http://www.checkupdown.com/status/E304.html" rel="nofollow">http://www.checkupdown.com/status/E304.html</a>
http://en.wikipedia.org/wiki/HTTP_ETag
<a href="http://www.xpertdeveloper.com/2011/03/last-modified-header-vs-expire-header-vs-etag/" rel="nofollow">http://www.xpertdeveloper.com/2011/03/last-modified-header-vs-expire-header-vs-etag/</a>

After reading I saw that there is also a expire date. If you have problem, it might be that you have a expire date set up. In other words, when the browser will cache your file, since it has a expiry date, it shouldn't have to request it again before that date. In other words, it will never ask the file to the server and will never receive a 304 not modified. It will simply use the cache until the expiry date is reached or cache is cleared.

So that is my guess, you have some sort of expiry date and you should use last-modified etags or a mix of it all and make sure that there is no expire date. 

If people tends to refresh a lot and the file doesn't get changed a lot, then it might be wise to set a big expiry date. 

My 2 cents!

blocks|key|1164868|text|我实现了这个适用于我的简单解决方案(还不适用于生产环境)：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1164869|function+verificarNovaVersio()+{
++++var+sVersio+=+localStorage['gcf_versio'%2B+location.pathname]+%7C%7C+'v00.0.0000';
++++$.ajax({
++++++++url:+"./versio.txt"
++++++++,+dataType:+'text'
++++++++,+cache:+false
++++++++,+contentType:+false
++++++++,+processData:+false
++++++++,+type:+'post'
+++++}).done(function(sVersioFitxer)+{
++++++++console.log('Versió+App:+'%2B+sVersioFitxer+%2B',+Versió+Caché:+'%2B+sVersio);
++++++++if+(sVersio+<+(sVersioFitxer+%7C%7C+'v00.0.0000'))+{
++++++++++++localStorage['gcf_versio'%2B+location.pathname]+=+sVersioFitxer;
++++++++++++location.reload(true);
++++++++}
++++});
}|code-block|syntax|javascript|1164870|我在html所在的位置有一个小文件：|1164871|"versio.txt"：|1164872|v00.5.0014|1164873|在我的所有页面中都会调用此函数，因此在加载它时，将检查localStorage的版本值是否低于当前版本，并执行|1164874|location.reload(true);|1164875|...to强制从服务器重新加载，而不是从缓存。|1164876|(显然，您可以使用cookies或其他持久性客户端存储来代替localStorage+)|1164877|我选择这个解决方案是因为它的简单性，因为只有一个文件"versio.txt“会强制整个站点重新加载。|1164878|queryString方法很难实现，而且也被缓存(如果您从v1.1更改为以前的版本将从缓存加载，那么这意味着缓存不会刷新，将所有以前的版本保持在缓存中)。|1164879|我是一个小菜鸟，我会感谢你的专业检查和审查，以确保我的方法是一个好的方法。|1164880|希望能有所帮助。|1164881|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|15|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|16|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|17|8|@]|9|@]|A|$]]|$1|K|3|L|5|D|7|18|8|@]|9|@]|A|$E|F]]|$1|M|3|N|5|6|7|19|8|@]|9|@]|A|$]]|$1|O|3|P|5|D|7|1A|8|@]|9|@]|A|$E|F]]|$1|Q|3|R|5|6|7|1B|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|1C|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1D|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|1E|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|1F|8|@]|9|@]|A|$]]|$1|10|3|11|5|6|7|1G|8|@]|9|@]|A|$]]|$1|12|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]]|13|$]]

I implemented this simple solution that works for me (not yet on production environment):

<pre><code>function verificarNovaVersio() {
 var sVersio = localStorage['gcf_versio'+ location.pathname] || 'v00.0.0000';
 $.ajax({
 url: "./versio.txt"
 , dataType: 'text'
 , cache: false
 , contentType: false
 , processData: false
 , type: 'post'
 }).done(function(sVersioFitxer) {
 console.log('Versió App: '+ sVersioFitxer +', Versió Caché: '+ sVersio);
 if (sVersio &lt; (sVersioFitxer || 'v00.0.0000')) {
 localStorage['gcf_versio'+ location.pathname] = sVersioFitxer;
 location.reload(true);
 }
 });
}
</code></pre>

I've a little file located where the html are:

"versio.txt":

<pre><code>v00.5.0014
</code></pre>

This function is called in all of my pages, so when loading it checks if the localStorage's version value is lower than the current version and does a 

<pre><code>location.reload(true);
</code></pre>

...to force reload from server instead from cache.

(obviously, instead of localStorage you can use cookies or other persistent client storage)

I opted for this solution for its simplicity, because only mantaining a single file "versio.txt" will force the full site to reload.

The queryString method is hard to implement and is also cached (if you change from v1.1 to a previous version will load from cache, then it means that the cache is not flushed, keeping all previous versions at cache).

I'm a little newbie and I'd apreciate your professional check &amp; review to ensure my method is a good approach.

Hope it helps.

blocks|key|1164594|text|除了设置Cache-control:+no-cache之外，如果您希望每次刷新本地副本，还应该将Expires标头设置为-1+(某些版本的IE似乎要求这样做)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1164595|请参阅HTTP+Cache+-+check+with+the+server,+always+sending+If-Modified-Since|offset|length|1164596|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/1917586/http-cache-check-with-the-server-always-sending-if-modified-since/1917827#1917827^0|0|3|1W|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

In addition to setting Cache-control: no-cache, you should also set the Expires header to -1 if you would like the local copy to be refreshed each time (some versions of IE seem to require this).

See <a href="https://stackoverflow.com/questions/1917586/http-cache-check-with-the-server-always-sending-if-modified-since/1917827#1917827">HTTP Cache - check with the server, always sending If-Modified-Since</a>

blocks|key|1164960|text|有一个技巧可以是used.The技巧，那就是在脚本标记中的文件名后附加一个参数/字符串，并在文件更改时对其进行更改。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1164961|<script+src="myfile.js?version=1.0.0"></script>|offset|length|style|CODE|1164962|浏览器会将整个字符串解释为文件路径，即使"?“是参数。因此，现在发生情况是，下次当您更新文件时，只需更改网站(例如<script+src="myfile.js?version=1.0.1"></script>)上的脚本标记中的编号，每个用户的浏览器都会看到该文件已更改，并抓取一个新的副本。|1164963|entityMap^0|0|0|1B|0|1L|1B|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@$D|Q|E|R|F|G]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|K|$]]

There is one trick that can be used.The trick is to append a parameter/string to the file name in the script tag and change it when you file changes.

<code>&lt;script src="myfile.js?version=1.0.0"&gt;&lt;/script&gt;</code>

The browser interprets the whole string as the file path even though what comes after the "?" are parameters. So wat happens now is that next time when you update your file just change the number in the script tag on your website (Example <code>&lt;script src="myfile.js?version=1.0.1"&gt;&lt;/script&gt;</code>) and each users browser will see the file has changed and grab a new copy.

blocks|key|1165098|text|如果你是Wordpress的开发者，我有一些好消息要告诉你。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1165099|只需搜索、安装并激活名为:+reBusted的Wordpress插件。|1165100|不需要配置。|1165101|如果内容已经更新，它会自动强制缓存刷新，它完全可靠地解决了这个问题。在数百个客户端上测试和使用Wordpress网站--在任何地方都能完美工作。|1165102|怎么推荐都不为过。|1165103|如果你使用Wordpress，这是你解决这个问题的最佳选择和最优雅的解决方案。|1165104|享受吧！|1165105|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|S|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|T|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|U|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|V|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|O|$]]

If you are a Wordpress developer I have some great news for you.
Just search for, install and activate the Wordpress plugin called: reBusted.
No configuration is necessary.
It will automatically force cache refresh if the content has been updated and it solves this issue completely and reliably. Tested and used on hundreds of clients Wordpress sites – works perfectly everywhere.
Cannot recommend it enough.
If you use Wordpress, this is by far your best option and most elegant resolution for this issue.
Enjoy!

blocks|key|1380124|text|对于webpack用户：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1380125|我在我的webpack配置中添加了chunkhash。这解决了我在每次部署时使缓存无效的问题。另外，我们需要注意的是，index.html/+asset.manifest不会被缓存到您的CDN或浏览器中。在webpack配置中的组块名称配置将如下所示：|1380126|块散列:fileName-${Date.now()}.js|1380127|或者如果你正在使用contenthash，那么|1380128|上下文:fileName-${Date.now()}.js|1380129|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

For webpack users:-
I added time with chunkhash in my webpack config. This solved my problem of invalidating cache on each deployment. Also we need to take care that index.html/ asset.manifest is not cached both in your CDN or browser. Config of chunk name in webpack config will look like this:-
fileName: [chunkhash]-${Date.now()}.js
or If you are using contenthash then
fileName: [contenthash]-${Date.now()}.js

blocks|key|1380190|text|这是我使用PHP在我的一个应用程序中解决的简单解决方案。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1380191|所有JS和CSS文件都放在一个带有版本名的文件夹中。示例："1.0.01“|1380192|root\1.0.01\JS
root\1.0.01\CSS|code-block|syntax|javascript|1380193|创建了一个帮助器并在其中定义了版本号|1380194|<?php
function+system_version()
{
++++return+'1.0.07';
}|1380195|链接的JS和SCC文件，如下所示|1380196|<script+src="<?=+base_url();+?>/<?=+system_version();?>/js/generators.js"+type="text/javascript"></script>
<link+rel="stylesheet"+type="text/css"+href="<?=+base_url();+?>/<?=+system_version();+?>/css/view-checklist.css"+/>|1380197|每当我对任何JS或CSS文件进行更改时，我都会在Helper中更改系统Verson，并重命名文件夹并部署它。|1380198|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|W|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|X|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|Y|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|Z|8|@]|9|@]|A|$]]|$1|O|3|P|5|F|7|10|8|@]|9|@]|A|$G|H]]|$1|Q|3|R|5|6|7|11|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|T|$]]

This is the simple solution I used to solve in one of my applications using PHP.
All JS and CSS files are placed in a folder with version name. Example : &quot;1.0.01&quot;
<pre><code>root\1.0.01\JS
root\1.0.01\CSS
</code></pre>
Created a Helper and Defined the version Number there
<pre><code>&lt;?php
function system_version()
{
 return '1.0.07';
}
</code></pre>
And Linked JS and SCC Files like below
<pre><code>&lt;script src=&quot;&lt;?= base_url(); ?&gt;/&lt;?= system_version();?&gt;/js/generators.js&quot; type=&quot;text/javascript&quot;&gt;&lt;/script&gt;
&lt;link rel=&quot;stylesheet&quot; type=&quot;text/css&quot; href=&quot;&lt;?= base_url(); ?&gt;/&lt;?= system_version(); ?&gt;/css/view-checklist.css&quot; /&gt;
</code></pre>
Whenever I make changes to any JS or CSS file, I change the System Verson in Helper and rename the folder and deploy it.

blocks|key|1164454|text|您是要清除缓存，还是只确保您的当前(已更改？)页面是否未缓存？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1164455|如果是后者，则应该像下面这样简单|1164456|<META+HTTP-EQUIV="Pragma"+CONTENT="no-cache">|code-block|syntax|javascript|1164457|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Do you want to clear the cache, or just make sure your current (changed?) page is not cached?

If the latter, it should be as simple as 

<pre><code>&lt;META HTTP-EQUIV="Pragma" CONTENT="no-cache"&gt;
</code></pre>

Is there a way I can put some code on my page so when someone visits a site, it clears the browser cache, so they can view the changes?

Languages used: ASP.NET, VB.NET, and of course HTML, CSS, and jQuery.

Force browser to clear cache

服务器

jQuery

有没有一种方法可以把一些代码放到我的页面上，这样当有人访问网站时，它就会清除浏览器缓存，这样他们就可以查看更改了？使用的语言: ASP.NET、VB.NET，当然还有HTML、CSS和jQuery。

问强制浏览器清除缓存
EN

回答 16

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问强制浏览器清除缓存EN

回答 16

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问强制浏览器清除缓存
EN