blocks|key|3829519|text|视情况而定。它应该是完整的网址，但一些浏览器(Opera，Safari)对具有不同参数的网址应用了不同的缓存策略。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3829520|最好的方法是更改文件的名称。|3829521|这里有一个非常聪明的解决方案(使用PHP、Apache)|3829522|http://verens.com/archives/2008/04/09/javascript-cache-problem-solved/|offset|length|3829523|策略说明：“根据超文本传输协议缓存规范的文字，用户代理永远不应该缓存带有查询字符串的URL。虽然Internet+Explorer和Firefox会忽略这一点，但Opera和Safari不会--为了确保所有用户代理都可以缓存您的资源，我们需要将查询字符串排除在它们的URL之外。|style|BOLD|3829524|http://www.thinkvitamin.com/features/webapps/serving-javascript-fast|3829525|entityMap|0|LINK|mutability|MUTABLE|url|1^0|0|0|0|0|1Y|0|0|0|5|0|0|1W|1|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Z|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|10|8|@]|9|@$H|11|I|12|1|13]]|A|$]]|$1|J|3|K|5|6|7|14|8|@$H|15|I|16|L|M]]|9|@]|A|$]]|$1|N|3|O|5|6|7|17|8|@]|9|@$H|18|I|19|1|1A]]|A|$]]|$1|P|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]]|Q|$R|$5|S|T|U|A|$V|G]]|W|$5|S|T|U|A|$V|O]]]]

depends. it is supposed to be the full URL, but some browsers (Opera, Safari<a href="http://www.thinkvitamin.com/features/webapps/serving-javascript-fast" rel="nofollow noreferrer">2</a>) apply a different cache strategy for urls with different params.

best bet is to change the name of the file.

There is a very clever solution here (uses PHP, Apache)

<a href="http://verens.com/archives/2008/04/09/javascript-cache-problem-solved/" rel="nofollow noreferrer">http://verens.com/archives/2008/04/09/javascript-cache-problem-solved/</a>

Strategy notes:
“According the letter of the HTTP caching specification, user agents should never cache URLs with query strings. While Internet Explorer and Firefox ignore this, Opera and Safari don’t - to make sure all user agents can cache your resources, we need to keep query strings out of their URLs.”

<a href="http://www.thinkvitamin.com/features/webapps/serving-javascript-fast" rel="nofollow noreferrer">http://www.thinkvitamin.com/features/webapps/serving-javascript-fast</a>

blocks|key|745560|text|我99.99999%25确定它是用于在浏览器中缓存资源的整个url，所以您的url方案应该工作得很好。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|745561|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I am 99.99999% sure that it is the entire url that is used to cache resources in a browser, so your url scheme should work out fine.

blocks|key|745576|text|是。从缓存的角度来看，不同的路径是相同的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|745577|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Yes. A different path is the same from the caches perspective.

blocks|key|2985462|text|当然，它必须使用完整的路径'/r20/example.js‘vs+'/r21/example.js’可以是完全不同的图像。您所建议的是一种处理版本控制的可行方法。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2985463|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Of course it has to use the whole path '/r20/example.js' vs '/r21/example.js' could be completely different images to begin with. What you suggest is a viable way to handle version control.

blocks|key|3829707|text|在大多数浏览器中，使用完整的url。在某些浏览器中，如果在url中有查询，则永远不会缓存文档。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3829708|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In most browsers the full url is used. 
In some browsers, if you have a query in the url, the document will never be cached.

blocks|key|745654|text|标识HTTP对象所需的最低要求是通过完整路径，包括任何查询字符串参数。有些浏览器可能不会缓存带有查询字符串的对象，但这与缓存的键无关。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|745655|同样重要的是要记住，路径不再足够。HTTP响应中的Vary:头向浏览器(或代理服务器等)发出警报。除URL以外的任何内容，如cookie、编码值等，用于确定缓存键。|745656|对于您的基本问题，是的，更改.js文件的URL就足够了。对于更大的问题是什么决定了缓存键，它是URL加上Vary:头限制。|745657|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

The MINIMUM you need to identify an HTTP object is by the full path, including any query-string parameters. Some browsers may not cache objects with a query string but that has nothing to do with the key to the cache.

It is also important to remember that the the path is no longer sufficient. The Vary: header in the HTTP response alerts the browser (or proxy server, etc.) of anything OTHER than the URL which should be used to determine the cache key, such as cookies, encoding values, etc.

To your basic question, yes, changing the URL of the .js file is sufficent. TO the larger question of what determines the cache key, it's the URL plus the Vary: header restrictions.

blocks|key|745675|text|整个url。我在一些较老的浏览器中看到了一种奇怪的行为，在这些浏览器中，区分大小写起了作用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|745676|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Entire url. I've seen a strange behavior in a few older browsers where case sensitivity came into play.

blocks|key|3829911|text|是的，URL的任何部分中的任何更改(+HTTP和HTTPS协议更改除外)都会被浏览器(和任何中间代理)解释为不同的资源，因此将在浏览器缓存中产生一个单独的实体。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3829912|更新：|offset|length|style|BOLD|3829913|在this+ThinkVitamin+article中，Opera和Safari/Webkit浏览器不使用?query=strings缓存URL的说法是false。|3829914|向URL添加版本号参数是一种完全可以接受的缓存破坏方式。|3829915|可能让ThinkVitamin文章的作者感到困惑的是，在Safari和Opera中按下地址/地址栏中的Enter会对包含查询字符串的URL产生不同的行为。|3829916|然而，(这是最重要的部分！)在缓存网页中嵌入/链接的图像、样式表和脚本时，Opera和Safari+的行为就像IE和Firefox一样--不管它们是否有"?“其URL中的字符。(这可以通过在正常的Apache服务器上进行简单的测试来验证。)|3829917|(如果我有这样做的声誉，我会对目前接受的答案发表评论。:-)|3829918|entityMap|0|LINK|mutability|MUTABLE|url|http://www.thinkvitamin.com/features/webapps/serving-javascript-fast^0|0|0|3|0|24|5|1|P|0|0|0|0|1E|F|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|10|8|@$D|11|E|12|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|13|8|@$D|14|E|15|F|G]]|9|@$D|16|E|17|1|18]]|A|$]]|$1|J|3|K|5|6|7|19|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|1A|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|1B|8|@$D|1C|E|1D|F|G]]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1E|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|1F|8|@]|9|@]|A|$]]]|S|$T|$5|U|V|W|A|$X|Y]]]]

Yes, any change in any part of the URL (excluding HTTP and HTTPS protocols changes) is interpreted as a different resource by the browser (and any intermediary proxies), and will thus result in a separate entity in the browser-cache.

Update:

The claim in <a href="http://www.thinkvitamin.com/features/webapps/serving-javascript-fast" rel="noreferrer">this ThinkVitamin article</a> that Opera and Safari/Webkit browsers don't cache URLs with ?query=strings is false.

Adding a version number parameter to a URL is a perfectly acceptable way to do cache-busting.

What may have confused the author of the ThinkVitamin article is the fact that hitting Enter in the address/location bar in Safari and Opera results in different behavior for URLs with query string in them.

However, (and this is the important part!) Opera and Safari behave just like IE and Firefox when it comes to caching embedded/linked images and stylesheets and scripts in web pages - regardless of whether they have "?" characters in their URLs. (This can be verified with a simple test on a normal Apache server.)

(I would have commented on the currently accepted answer if I had the reputation to do it. :-)

blocks|key|5240460|text|浏览器缓存键是请求方法和资源URI的组合。URI由方案、权限、路径、查询和片段组成。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5240461|相关摘录自HTTP+1.1+specification|offset|length|5240462|5240463|主缓存键由请求方法和目标URI组成。然而，由于目前常用的HTTP缓存通常仅限于缓存要获取的响应，因此许多缓存只是拒绝其他方法，而只使用URI作为主缓存键。|blockquote|5240464|5240465|5240466|相关摘录自URI+specification|5240467|5240468|通用URI语法由称为方案、授权、路径、查询和片段的组件的分层序列组成。URI+=+scheme+":“hier-part+"?”query+hier-part+=+"//“权限路径-abempty|5240469|5240470|5240471|++++++++++++++/+path-absolute
++++++++++++++/+path-rootless
++++++++++++++/+path-empty|code-block|syntax|javascript|5240472|entityMap|0|LINK|mutability|MUTABLE|url|https://www.rfc-editor.org/rfc/rfc7234#section-2|1|https://www.rfc-editor.org/rfc/rfc3986#section-3^0|0|5|M|0|0|0|0|0|0|5|H|1|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|17|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|18|8|@]|9|@$D|19|E|1A|1|1B]]|A|$]]|$1|F|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]|$1|G|3|H|5|I|7|1D|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|1E|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|1F|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|1G|8|@]|9|@$D|1H|E|1I|1|1J]]|A|$]]|$1|N|3|-4|5|6|7|1K|8|@]|9|@]|A|$]]|$1|O|3|P|5|I|7|1L|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|1M|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|1N|8|@]|9|@]|A|$]]|$1|S|3|T|5|U|7|1O|8|@]|9|@]|A|$V|W]]|$1|X|3|-4|5|6|7|1P|8|@]|9|@]|A|$]]]|Y|$Z|$5|10|11|12|A|$13|14]]|15|$5|10|11|12|A|$13|16]]]]

Browser cache key is a combination of the request method and resource URI. URI consists of scheme, authority, path, query, and fragment.
Relevant excerpt from <a href="https://www.rfc-editor.org/rfc/rfc7234#section-2" rel="nofollow noreferrer">HTTP 1.1 specification</a>:
<blockquote>
The primary cache key consists of the request method and target URI.
However, since HTTP caches in common use today are typically limited
to caching responses to GET, many caches simply decline other methods
and use only the URI as the primary cache key.
</blockquote>
Relevant excerpt from <a href="https://www.rfc-editor.org/rfc/rfc3986#section-3" rel="nofollow noreferrer">URI specification</a>:
<blockquote>
The generic URI syntax consists of a hierarchical sequence of
components referred to as the scheme, authority, path, query, and
fragment.
</blockquote>
<blockquote>
<pre><code>URI = scheme &quot;:&quot; hier-part [ &quot;?&quot; query ] [ &quot;#&quot; fragment ]
</code></pre>
</blockquote>
<blockquote>
<pre><code>hier-part = &quot;//&quot; authority path-abempty
</code></pre>
</blockquote>
<pre><code> / path-absolute
 / path-rootless
 / path-empty
</code></pre>

blocks|key|749215|text|除了现有的答案之外，我只想补充说，如果你使用ServiceWorkers或离线插件，它可能不适用。然后，您可能会体验到不同的缓存规则，具体取决于ServiceWorkers的设置方式。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|749216|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In addition to the existing answers I just want to add that it might not apply if you use ServiceWorkers or e.g offline-plugin. Then you could experience different cache rules depending on how the ServiceWorkers are set up.

It's common to want browsers to cache resources - JavaScript, CSS, images, etc. until there is a new version available, and then ensure that the browser fetches and caches the new version instead.

One solution is to embed a version number in the resource's filename, but will placing the resources to be managed in this way in a directory with a revision number in it do the same thing? Is the whole URL to the file used as a key in the browser's cache, or is it just the filename itself and some meta-data?

If my code changes from fetching <code>/r20/example.js</code> to <code>/r21/example.js</code>, can I be sure that revision 20 of <code>example.js</code> was cached, but now revision 21 has been fetched instead and it is now cached?

Is it the filename or the whole URL used as a key in browser caches?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

通常希望浏览器缓存资源- JavaScript、CSS、图像等，直到有新版本可用，然后确保浏览器获取并缓存新版本。一种解决方案是在资源的文件名中嵌入一个版本号，但是将以这种方式管理的资源放在一个带有修订号的目录中会做同样的事情吗？文件的整个URL是用作浏览器缓存中的关键字，还是仅仅是文件名本身和一些元数据？如果我的代码...

问它是文件名还是浏览器缓存中用作关键字的整个URL？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问它是文件名还是浏览器缓存中用作关键字的整个URL？EN